diff --git a/search.py b/search.py new file mode 100644 index 0000000..716bc2c --- /dev/null +++ b/search.py @@ -0,0 +1,663 @@ +""" +DevRev Search — BM42 Hybrid Retrieval with Haystack + Qdrant. + +Hybrid search system combining sparse (BM42) and dense (mxbai-embed-large-v1) +embeddings for information retrieval on the DevRev knowledge base. + +Indexing Pipeline: + DocumentCleaner + → FastembedSparseDocumentEmbedder (BM42) + → SentenceTransformersDocumentEmbedder (mxbai-embed-large-v1, 1024-dim) + → DocumentWriter (Qdrant) + +Retrieval Pipeline: + FastembedSparseTextEmbedder (BM42) + + SentenceTransformersTextEmbedder (mxbai-embed-large-v1) + → QdrantHybridRetriever (RRF fusion, top_k=RETRIEVER_TOP_K) + → adjacent-chunk expansion (±1 KNOWLEDGE_NODE neighbour) + → SentenceTransformersSimilarityRanker (bge-reranker-v2-m3, top_k=TOP_K) + +Evaluation: + run_annotated_evaluation() scores Recall@10, Precision@10, MRR@10, NDCG@10 + against annotated_queries (291 labelled queries). + +Mac-specific notes: + - BATCH_SIZE = 32 (avoids MPS OOM on Apple Silicon) + - device = "mps" (Metal GPU acceleration via PyTorch) + - sentence-transformers picks up MPS automatically +""" + +import json +import logging +import re +from enum import Enum + +import pandas as pd +from datasets import load_dataset +from tqdm import tqdm +from qdrant_client import QdrantClient + +# Haystack core imports +from haystack import Document, Pipeline +from haystack.components.preprocessors import DocumentCleaner +from haystack.components.rankers import SentenceTransformersSimilarityRanker +from haystack.components.writers import DocumentWriter +from haystack.document_stores.types import DuplicatePolicy + +# Qdrant document store and retriever +from haystack_integrations.document_stores.qdrant import QdrantDocumentStore +from haystack_integrations.components.retrievers.qdrant import QdrantHybridRetriever + +# Embedders +from haystack.components.embedders import ( + SentenceTransformersDocumentEmbedder, + SentenceTransformersTextEmbedder, +) +from haystack_integrations.components.embedders.fastembed import ( + FastembedSparseDocumentEmbedder, + FastembedSparseTextEmbedder, +) + +# ------------------------------------------- +# Logging +# ------------------------------------------- +logger = logging.getLogger(__name__) + + +def configure_logging(level: int = logging.INFO) -> None: + """Configure logging with a consistent format.""" + handler = logging.StreamHandler() + formatter = logging.Formatter( + "[%(asctime)s] %(levelname)-8s %(name)s: %(message)s", + datefmt="%Y-%m-%d %H:%M:%S", + ) + handler.setFormatter(formatter) + logger.addHandler(handler) + logger.setLevel(level) + + +# ------------------------------------------- +# Configuration +# ------------------------------------------- + +# Mac / Apple Silicon: keep batches small to stay within MPS memory budget. +# On CPU-only machines this can safely go up to 128–256. +BATCH_SIZE = 32 + +EMBEDDING_DIM = 1024 + +# Dense bi-encoder (indexing + retrieval) +DENSE_MODEL = "mixedbread-ai/mxbai-embed-large-v1" +DENSE_QUERY_PREFIX = "Represent this sentence for searching relevant passages: " + +# Sparse bi-encoder (BM42) +SPARSE_MODEL = "Qdrant/bm42-all-minilm-l6-v2-attentions" + +# Cross-encoder reranker. +# bge-reranker-v2-m3 outperforms ms-marco-MiniLM on BEIR/MIRACL but is heavier. +# On Mac CPU it is ~3–4× slower than MiniLM; swap if latency matters more than quality: +# RERANKER_MODEL = "cross-encoder/ms-marco-MiniLM-L6-v2" +RERANKER_MODEL = "BAAI/bge-reranker-v2-m3" + +# Qdrant connection +QDRANT_HOST = "localhost" +QDRANT_PORT = 6333 +COLLECTION_NAME = "devrev_search" + +# Retriever fetches a wide candidate pool; reranker then trims to TOP_K. +# Higher RETRIEVER_TOP_K → better recall ceiling, slower reranker step. +RETRIEVER_TOP_K = 50 +TOP_K = 10 # final results returned per query + +# Adjacent-chunk expansion: include ±NEIGHBOUR_WINDOW KNOWLEDGE_NODEs around +# each retrieved chunk. Boosts recall when answers span consecutive nodes. +# Set to 0 to disable. +NEIGHBOUR_WINDOW = 1 + +# Output files (test_queries submission) +OUTPUT_JSON = "test_queries_results.json" +OUTPUT_PARQUET = "test_queries_results.parquet" + + +# ------------------------------------------- +# Dataset helpers +# ------------------------------------------- +class DatasetType(Enum): + ANNOTATED_QUERIES = "annotated_queries" + TEST_QUERIES = "test_queries" + KNOWLEDGE_BASE = "knowledge_base" + + +def get_dataset(dataset_type: DatasetType) -> pd.DataFrame: + """Load a split of devrev/search and return as a DataFrame.""" + if dataset_type == DatasetType.ANNOTATED_QUERIES: + df = load_dataset("devrev/search", "annotated_queries") + return df["train"].to_pandas() + elif dataset_type == DatasetType.TEST_QUERIES: + df = load_dataset("devrev/search", "test_queries") + return df["test"].to_pandas() + elif dataset_type == DatasetType.KNOWLEDGE_BASE: + df = load_dataset("devrev/search", "knowledge_base") + return df["corpus"].to_pandas() + else: + raise ValueError(f"Unknown dataset type: {dataset_type}") + + +# ------------------------------------------- +# Text cleaning helpers +# ------------------------------------------- +_BYTE_PREFIX = re.compile(r"""^b['\"](.*)['\"]\\s*$""", re.DOTALL) + + +def clean_text(raw: str) -> str: + """Strip Python byte-string artifacts and normalise whitespace. + + Some knowledge-base chunks are serialised as b'actual text here' + (a Python bytes repr leaked into the dataset). This strips the wrapper + so the embedder sees clean prose rather than a Python literal. + """ + if not isinstance(raw, str): + return "" + m = _BYTE_PREFIX.match(raw.strip()) + if m: + # Unescape common escape sequences preserved in the repr + text = m.group(1) + text = text.replace("\\n", "\n").replace("\\t", "\t") + text = text.replace("\'", "'").replace('\\"', '"') + return text.strip() + return raw.strip() + + +def build_content(title: str, text: str) -> str: + """Concatenate title + text for indexing. + + Prepending the title gives the embedding model full article context and + ensures product-specific terms (e.g. "AirSync", "snap-in") appear in + every chunk, not just the first one. + """ + title = (title or "").strip() + text = clean_text(text or "") + if title: + return f"{title}\n\n{text}" + return text + + +# ------------------------------------------- +# Adjacent-chunk expansion +# ------------------------------------------- +_NODE_RE = re.compile(r"^(ART-\d+)_KNOWLEDGE_NODE-(\d+)$") + + +def expand_with_neighbours( + doc_ids: list[str], + id_to_doc: dict[str, Document], + window: int = NEIGHBOUR_WINDOW, +) -> list[Document]: + """Expand a retrieved set with adjacent KNOWLEDGE_NODE chunks. + + IDs follow the pattern ART-_KNOWLEDGE_NODE-. + For each retrieved chunk we also include ±window neighbours from the same + article, then deduplicate while preserving retrieval-rank order. + + Args: + doc_ids: Ordered list of retrieved document IDs (best first). + id_to_doc: Mapping of all indexed doc_id → Document. + window: How many adjacent nodes to include on each side. + + Returns: + Deduplicated list of Documents (retrieved + neighbours), original + order preserved, neighbours inserted immediately after their source. + """ + if window == 0: + return [id_to_doc[d] for d in doc_ids if d in id_to_doc] + + seen: set[str] = set() + result: list[Document] = [] + + for doc_id in doc_ids: + m = _NODE_RE.match(doc_id) + if not m: + # ID does not follow the expected pattern — include as-is + if doc_id not in seen and doc_id in id_to_doc: + seen.add(doc_id) + result.append(id_to_doc[doc_id]) + continue + + art_prefix, node_idx = m.group(1), int(m.group(2)) + + # Build candidate IDs: retrieved chunk + its neighbours + candidates = [ + f"{art_prefix}_KNOWLEDGE_NODE-{node_idx + delta}" + for delta in range(-window, window + 1) + ] + + for cid in candidates: + if cid not in seen and cid in id_to_doc: + seen.add(cid) + result.append(id_to_doc[cid]) + + return result + + +# ------------------------------------------- +# Document store +# ------------------------------------------- +def get_document_store(recreate: bool = False) -> QdrantDocumentStore: + """Get or create a QdrantDocumentStore for hybrid search. + + When recreate=True we explicitly drop the collection via raw QdrantClient + first. This bypasses a silent failure in recreate_index=True when the + qdrant-client version (1.17) is newer than the server (1.9). + """ + if recreate: + raw_client = QdrantClient( + host=QDRANT_HOST, + port=QDRANT_PORT, + check_compatibility=False, + ) + existing = {c.name for c in raw_client.get_collections().collections} + if COLLECTION_NAME in existing: + raw_client.delete_collection(COLLECTION_NAME) + logger.info(f"Dropped existing Qdrant collection '{COLLECTION_NAME}'.") + raw_client.close() + + return QdrantDocumentStore( + host=QDRANT_HOST, + port=QDRANT_PORT, + index=COLLECTION_NAME, + embedding_dim=EMBEDDING_DIM, + use_sparse_embeddings=True, + recreate_index=recreate, + similarity="cosine", + return_embedding=False, + ) + + +# ------------------------------------------- +# Indexing pipeline +# ------------------------------------------- +def build_indexing_pipeline(document_store: QdrantDocumentStore) -> Pipeline: + """Build the indexing pipeline. + + DocumentCleaner + → FastembedSparseDocumentEmbedder (BM42 sparse vectors) + → SentenceTransformersDocumentEmbedder (mxbai dense, 1024-dim, MPS) + → DocumentWriter + """ + cleaner = DocumentCleaner( + remove_empty_lines=True, + remove_extra_whitespaces=True, + remove_repeated_substrings=False, + ) + + sparse_doc_embedder = FastembedSparseDocumentEmbedder( + model=SPARSE_MODEL, + batch_size=BATCH_SIZE, + ) + + dense_doc_embedder = SentenceTransformersDocumentEmbedder( + model=DENSE_MODEL, + batch_size=BATCH_SIZE, + ) + + writer = DocumentWriter( + document_store=document_store, + policy=DuplicatePolicy.OVERWRITE, + ) + + indexing = Pipeline() + indexing.add_component("cleaner", cleaner) + indexing.add_component("sparse_doc_embedder", sparse_doc_embedder) + indexing.add_component("dense_doc_embedder", dense_doc_embedder) + indexing.add_component("writer", writer) + + indexing.connect("cleaner.documents", "sparse_doc_embedder.documents") + indexing.connect("sparse_doc_embedder.documents", "dense_doc_embedder.documents") + indexing.connect("dense_doc_embedder.documents", "writer.documents") + + return indexing + + +def index_knowledge_base(document_store: QdrantDocumentStore) -> None: + """Load, clean, and index the DevRev knowledge base. + + Improvements applied at index time + ------------------------------------ + 1. b\'...' byte-string stripping — clean_text() + 2. Title + text concatenation — build_content() + Prepending the title ensures every chunk carries article-level keywords + ("AirSync", "snap-in") that may only appear in the title of later nodes. + 3. Null/empty row filtering — avoids DocumentCleaner warning spam. + + Metadata stored + --------------- + doc_id : original corpus ID (e.g. ART-4216_KNOWLEDGE_NODE-26) + title : article title (used for output and neighbour expansion) + art_id : article prefix (e.g. ART-4216, for grouping/boosting) + node_idx : integer chunk index (for neighbour expansion ordering) + source : provenance string + """ + kb_df = get_dataset(DatasetType.KNOWLEDGE_BASE) + + # Filter nulls upfront — DocumentCleaner would skip them but logs a + # warning for every single one, flooding the output. + original_count = len(kb_df) + kb_df = kb_df[kb_df["text"].notna() & (kb_df["text"].str.strip() != "")] + dropped = original_count - len(kb_df) + if dropped: + logger.warning(f"Dropped {dropped} row(s) with null/empty text.") + + documents: list[Document] = [] + for _, row in kb_df.iterrows(): + doc_id: str = row["id"] + title: str = row.get("title", "") or "" + raw_text: str = row["text"] + + # Parse ART-XXXX_KNOWLEDGE_NODE-YY for metadata + m = _NODE_RE.match(doc_id) + art_id = m.group(1) if m else doc_id + node_idx = int(m.group(2)) if m else 0 + + content = build_content(title, raw_text) + + doc = Document( + content=content, + meta={ + "doc_id": doc_id, + "title": title, + "art_id": art_id, + "node_idx": node_idx, + "source": "devrev/search::knowledge_base", + }, + ) + documents.append(doc) + + logger.info(f"Indexing {len(documents):,} documents …") + indexing_pipeline = build_indexing_pipeline(document_store) + indexing_pipeline.run({"cleaner": {"documents": documents}}) + logger.info(f"Indexed {len(documents):,} documents into Qdrant.") + + +# ------------------------------------------- +# Retrieval pipeline +# ------------------------------------------- +def build_retrieval_pipeline(document_store: QdrantDocumentStore) -> Pipeline: + """Build the hybrid retrieval + reranking pipeline. + + query + ├─ FastembedSparseTextEmbedder → query_sparse_embedding ─┐ + └─ SentenceTransformersTextEmbedder → query_embedding ─┤ + ↓ + QdrantHybridRetriever (RRF, top_k=RETRIEVER_TOP_K) + ↓ + [adjacent-chunk expansion in search()] + ↓ + SentenceTransformersSimilarityRanker (top_k=TOP_K) + """ + sparse_text_embedder = FastembedSparseTextEmbedder( + model=SPARSE_MODEL, + ) + + dense_text_embedder = SentenceTransformersTextEmbedder( + model=DENSE_MODEL, + prefix=DENSE_QUERY_PREFIX, + ) + + retriever = QdrantHybridRetriever( + document_store=document_store, + top_k=RETRIEVER_TOP_K, + ) + + # Cross-encoder reranker: reads query + document text jointly with full + # cross-attention — significantly sharper relevance signals than bi-encoder + # cosine similarity alone. + reranker = SentenceTransformersSimilarityRanker( + model=RERANKER_MODEL, + top_k=TOP_K, + ) + + retrieval = Pipeline() + retrieval.add_component("sparse_text_embedder", sparse_text_embedder) + retrieval.add_component("dense_text_embedder", dense_text_embedder) + retrieval.add_component("retriever", retriever) + retrieval.add_component("reranker", reranker) + + retrieval.connect( + "sparse_text_embedder.sparse_embedding", + "retriever.query_sparse_embedding", + ) + retrieval.connect( + "dense_text_embedder.embedding", + "retriever.query_embedding", + ) + retrieval.connect("retriever.documents", "reranker.documents") + + return retrieval + + +def search( + query: str, + retrieval_pipeline: Pipeline, + id_to_doc: dict[str, Document] | None = None, +) -> list[dict]: + """Run a hybrid search query and return ranked results. + + Flow: + 1. Embed query (sparse + dense) and retrieve RETRIEVER_TOP_K candidates. + 2. Expand each candidate with ±NEIGHBOUR_WINDOW adjacent chunks from the + same article (improves recall when answers span multiple nodes). + 3. Rerank the expanded set with the cross-encoder (top_k=TOP_K). + + Args: + query: Natural-language search query. + retrieval_pipeline: Warmed-up Haystack Pipeline. + id_to_doc: Optional mapping of doc_id → Document for neighbour + expansion. If None, expansion is skipped. + + Returns: + List of dicts with keys: id, text, title (TOP_K entries). + """ + result = retrieval_pipeline.run( + { + "sparse_text_embedder": {"text": query}, + "dense_text_embedder": {"text": query}, + "reranker": {"query": query}, + } + ) + + reranked_docs: list[Document] = result["reranker"]["documents"] + + # --- Adjacent-chunk expansion (post-rerank) ---------------------------- + # We expand AFTER the reranker so the cross-encoder scores the clean + # retrieval set. Neighbours are appended at the end only if they are not + # already present in the reranked top-k. + if id_to_doc and NEIGHBOUR_WINDOW > 0: + ranked_ids = [d.meta["doc_id"] for d in reranked_docs] + expanded = expand_with_neighbours(ranked_ids, id_to_doc, NEIGHBOUR_WINDOW) + # Trim back to TOP_K after expansion + final_docs = expanded[:TOP_K] + else: + final_docs = reranked_docs[:TOP_K] + + return [ + { + "id": doc.meta.get("doc_id", ""), + "text": doc.content or "", + "title": doc.meta.get("title", ""), + } + for doc in final_docs + ] + + +# ------------------------------------------- +# Build id_to_doc lookup for neighbour expansion +# ------------------------------------------- +def build_id_to_doc(document_store: QdrantDocumentStore) -> dict[str, Document]: + """Fetch all documents from Qdrant and build a doc_id → Document mapping. + + Used by expand_with_neighbours() to look up adjacent chunks without + hitting Qdrant for every neighbour individually. + + Note: loads all 65 k documents into memory (~500 MB). Fine on a Mac with + ≥16 GB RAM; reduce NEIGHBOUR_WINDOW to 0 if memory is tight. + """ + logger.info("Building id→doc lookup table for neighbour expansion …") + all_docs = document_store.filter_documents() + mapping = {doc.meta["doc_id"]: doc for doc in all_docs if "doc_id" in doc.meta} + logger.info(f"Lookup table ready: {len(mapping):,} documents.") + return mapping + + +# ------------------------------------------- +# Test-query evaluation (submission output) +# ------------------------------------------- +def run_evaluation( + retrieval_pipeline: Pipeline, + id_to_doc: dict[str, Document] | None = None, + output_json: str = OUTPUT_JSON, + output_parquet: str = OUTPUT_PARQUET, +) -> list[dict]: + """Run retrieval on all test queries and save submission files.""" + test_df = get_dataset(DatasetType.TEST_QUERIES) + test_results: list[dict] = [] + + for _, row in tqdm( + test_df.iterrows(), total=len(test_df), desc="Evaluating test queries" + ): + retrievals = search(row["query"], retrieval_pipeline, id_to_doc) + test_results.append( + { + "query_id": row["query_id"], + "query": row["query"], + "retrievals": retrievals, + } + ) + + with open(output_json, "w") as f: + json.dump(test_results, f, indent=2) + logger.info(f"Results saved to {output_json}") + + pd.DataFrame(test_results).to_parquet(output_parquet, index=False) + logger.info(f"Results saved to {output_parquet}") + + logger.info(f"Total queries: {len(test_results)} | Retrievals/query: {TOP_K}") + return test_results + + +# ------------------------------------------- +# Annotated-query evaluation (recall / precision) +# ------------------------------------------- +def run_annotated_evaluation( + retrieval_pipeline: Pipeline, + id_to_doc: dict[str, Document] | None = None, +) -> dict: + """Score the pipeline against annotated_queries (291 labelled pairs). + + Uses ranx for standard IR metrics. Install with: + pip install ranx + + Metrics computed + ---------------- + Recall@10 — fraction of golden docs retrieved in top-10 (primary) + Precision@10 — fraction of top-10 that are golden docs + MRR@10 — mean reciprocal rank of first golden doc + NDCG@10 — rank-discounted cumulative gain + + Returns: + Dict mapping metric name → float score. + """ + try: + from ranx import Qrels, Run, evaluate + except ImportError: + logger.error("ranx is not installed. Run: pip install ranx") + raise + + annotated_df = get_dataset(DatasetType.ANNOTATED_QUERIES) + + # Build ground-truth Qrels: {query_id: {doc_id: 1}} + qrels_dict: dict[str, dict[str, int]] = {} + for _, row in annotated_df.iterrows(): + qid = str(row["query_id"]) + qrels_dict[qid] = {str(r["id"]): 1 for r in row["retrievals"]} + + qrels = Qrels(qrels_dict) + + # Build Run: {query_id: {doc_id: score}} + # Scores are descending rank positions (TOP_K, TOP_K-1, …, 1). + run_dict: dict[str, dict[str, float]] = {} + for _, row in tqdm( + annotated_df.iterrows(), + total=len(annotated_df), + desc="Scoring annotated queries", + ): + qid = str(row["query_id"]) + retrievals = search(row["query"], retrieval_pipeline, id_to_doc) + run_dict[qid] = { + str(r["id"]): float(TOP_K - i) + for i, r in enumerate(retrievals) + } + + run = Run(run_dict) + + metrics = evaluate( + qrels, + run, + ["recall@10", "precision@10", "mrr@10", "ndcg@10"], + ) + + logger.info("=" * 50) + logger.info("Retrieval evaluation — annotated_queries (291 queries)") + logger.info("=" * 50) + for k, v in metrics.items(): + logger.info(f" {k:<20} {v:.4f}") + logger.info("=" * 50) + + return dict(metrics) + + +# ------------------------------------------- +# Main +# ------------------------------------------- +def main() -> None: + """End-to-end flow. + + Steps + ----- + 1. Drop + recreate Qdrant collection and index the knowledge base. + → Set recreate=False on subsequent runs to skip re-indexing. + 2. Build retrieval pipeline (sparse + dense + reranker). + 3. Build id→doc lookup for neighbour expansion. + 4. Score against annotated_queries (Recall / Precision / MRR / NDCG). + 5. Run on test_queries and save submission JSON + Parquet. + """ + configure_logging(level=logging.INFO) + logger.info("Starting DevRev Search …") + + try: + # ── Step 1 : Index ───────────────────────────────────────────────── + # Flip to recreate=False once the collection is already indexed. + document_store = get_document_store(recreate=False) + index_knowledge_base(document_store) + + # ── Step 2 : Retrieval pipeline ──────────────────────────────────── + retrieval_pipeline = build_retrieval_pipeline(document_store) + + # ── Step 3 : Neighbour-expansion lookup ──────────────────────────── + id_to_doc = build_id_to_doc(document_store) + + # ── Step 4 : Score on annotated_queries ──────────────────────────── + logger.info("Running evaluation on annotated_queries …") + run_annotated_evaluation(retrieval_pipeline, id_to_doc) + + # ── Step 5 : Generate test_queries submission ─────────────────────── + logger.info("Generating test_queries submission …") + run_evaluation(retrieval_pipeline, id_to_doc) + + logger.info("Done.") + except Exception as e: + logger.error(f"Pipeline error: {e}", exc_info=True) + raise + + +if __name__ == "__main__": + main() diff --git a/test_queries_results.json b/test_queries_results.json index 74c199a..4971585 100644 --- a/test_queries_results.json +++ b/test_queries_results.json @@ -4,54 +4,54 @@ "query": "end customer organization name not appearing in ticket or conversation", "retrievals": [ { - "id": "ART-1981_KNOWLEDGE_NODE-30", - "text": "conversation of which you are not the owner, let the owner know to respond. It's beneficial to retain the same point of contact for the duration of the conversation unless the owner refers some another user.\\n* If the conversation has a customer org that's unidentified or is new, add yourself (the customer experience engineer) as the owner of the ticket. Try to find the appropriate owner for the customer org and update the customer record accordingly.\\n* Change the stage of the conversation to", - "title": "Support best practices | Computer for Support Teams | DevRev" + "id": "ART-1978_KNOWLEDGE_NODE-44", + "text": "URL and not on the support portal of some other customer.\\n* Customer admin isn't able to see all the tickets of the organization.\\n\\n + This could happen if the customer isn't logged in on the correct URL. If the customer is logged in on the correct URL, then check if there are any tickets that are reported by the other customers in that organization or not. Check if the customer is added as a customer admin or not by logging in to your DevRev application.\\n* You are not able to add customer", + "title": "Customer portal | Computer for Support Teams | DevRev" }, { - "id": "ART-1981_KNOWLEDGE_NODE-34", - "text": "ticket.\\n* Make sure all tickets have the customer org field populated.\\n* Cancel any internal ticket without a customer org that has been created by a developer. Ask them to create an issue instead.\\n* If a customer raises a feature request that aligns with the product strategy, but needs significant development effort and will not be delivered in the near future, move it to the *accepted* stage, rather than keeping the ticket open. Inform the customer accordingly.\\n* If a customer reports a", - "title": "Support best practices | Computer for Support Teams | DevRev" + "id": "ART-1986_KNOWLEDGE_NODE-45", + "text": "selected on the ticket is not assigned any SLA.\\n\\n\\xc2\\xa0\\xc2\\xa0 \\xc2\\xa0 - Action: Check your SLA assignment rules or add the customer as an exception to any of your SLAs.\\n\\n![]()\\n\\nThe **SLA Name** is never empty if your organization has a default SLA.\\n\\n1. Verify policy conditions:\\n\\n\\xc2\\xa0\\xc2\\xa0 - If the **SLA Name** is populated but you still see no SLA metrics running on the ticket, the ticket does not satisfy the conditions of any policy within the SLA.\\n\\n\\xc2\\xa0\\xc2\\xa0", + "title": "Service-level agreement | Computer for Support Teams | DevRev" }, { - "id": "ART-1953_KNOWLEDGE_NODE-30", - "text": "linked to a conversation\\n-------------------------------\\n\\n* **Trigger**: A ticket is linked to an existing conversation.\\n* **Action**: The system sends out a notification with the linked ticket number.\\n* **Sender**: {Company\\\\_Name} [support@yourdomain.com](mailto:support@yourdomain.com)\\n* **Subject**: \"\"\\n\\n![]()\\n\\nThis email is only sent to the organizations with [Convergence snap-in](https://docs.devrev.ai/automations/converge)\\n\\nChange of", - "title": "Customer email notifications | Computer by DevRev | DevRev" + "id": "ART-2002_KNOWLEDGE_NODE-25", + "text": "about the customer initiating the conversation. Similarly, tickets on DevRev can capture who the ticket was reported by (or reported for).\\n\\nConcepts\\n--------\\n\\nCustomer identity in DevRev includes the following important constructs:\\n\\n* **External User/contact**: Your end user or customer or users associated with organization Accounts or Workspaces.\\n* **Account/workspace**: Any logical grouping that an external user is part of. It could represent a customer account for your B2B product", + "title": "Contacts | Computer for Growth Teams | DevRev" }, { - "id": "ART-1953_KNOWLEDGE_NODE-29", - "text": "[support@yourdomain.com](mailto:support@yourdomain.com)\\n* **Subject**: \"You are missing messages from \"\\n\\nReply to the customer on a ticket\\n---------------------------------\\n\\n* **Trigger**: When a reply is made to a customer on a ticket.\\n* **Action**: The system sends out a notification to the customer with the reply message.\\n* **Sender**: {Company\\\\_Name} [support@yourdomain.com](mailto:support@yourdomain.com)\\n* **Subject**: \"[{Company\\\\_Name}] Update on TKT-XXX\"\\n\\nTicket", - "title": "Customer email notifications | Computer by DevRev | DevRev" + "id": "ART-16806_KNOWLEDGE_NODE-27", + "text": "Internal Ticket** from the **Ticket Creation** dropdown.\\n* **Focused UI:** The **Customer Messages** tab is disabled on internal tickets to prevent unintended communication.\\n\\nThis feature supports internal workflows while giving you control over when customer engagement begins.\\n\\n![]()\\xc2\\xa0For more information about *Conversation and Ticket Workflows*, refer to the following articles: \\xe2\\x80\\xa3 [Auto parts to conversation | Automate | Snap-ins](/docs/automations/auto-parts)", + "title": "July 2025 | Changelog | DevRev" }, { - "id": "ART-1953_KNOWLEDGE_NODE-5", - "text": "ticket conversion](/docs/product/conversation-ticket)\\n + [Tickets](/docs/product/tickets)\\n + [Routing](/docs/product/routing)\\n + [Support best practices](/docs/product/support-bp)\\n + [Customer portal](/docs/product/support-portal)\\n + [Questions & answers](/docs/product/qa)\\n + [Knowledge Base](/docs/product/knowledge-base)\\n\\n - [Articles](/docs/product/articles)\\n - [Collections](/docs/product/collection)\\n + [Turing AI agent](/docs/product/conversational-bot)\\n\\n - [Best", - "title": "Customer email notifications | Computer by DevRev | DevRev" + "id": "ART-2024_KNOWLEDGE_NODE-27", + "text": "help now... ask again in 5d\\n\\nSample response:\\n\\n> I am unable to assist you at the moment, however please reach out to me again in five days and I will be happy to help you.\\n\\n### Summarize\\n\\nUsing the summarize command, you can sum up the entire conversation. It applies to the following:\\n\\n* Conversation\\n* Tickets\\n* Issues\\n* Part\\n* Workspace\\n* Customer\\n* Account\\n\\nSample response:\\n\\n> **Summary:**\\n>\\n> * Rahul from DummyOrg is having difficulty installing the Plug Widget.\\n> *", + "title": "Slash commands | Automate | Snap-ins | DevRev" }, { - "id": "ART-1979_KNOWLEDGE_NODE-63", - "text": "support tickets on behalf of customers\\xe2\\x80\\x94without granting customers access to these tickets. This feature enables internal collaboration while keeping the ticket invisible to the customer until explicitly made external.\\n\\nEven if a ticket contains customer-related information (such as the customer workspace or the **Reported by** field), it remains inaccessible to the customer unless it is explicitly converted into an external ticket. The **Customer Messages** tab is unavailable for", - "title": "Tickets | Computer for Support Teams | DevRev" + "id": "ART-1978_KNOWLEDGE_NODE-33", + "text": "tickets but also all the tickets raised by the other users from their organization. You can add multiple customer admins from the same customer organization.\\n\\nOnly verified users can login into the portal.\\n\\nTo create a verified user:\\n\\n1. Go to **Accounts** in the DevRev app and create an account.\\n2. Create a contact under **Contacts** and link it to the account.\\n\\n### Set up customer admins\\n\\nTo set up customer admins, follow these steps:\\n\\n1. Log in on your DevRev app with your", + "title": "Customer portal | Computer for Support Teams | DevRev" }, { - "id": "ART-1978_KNOWLEDGE_NODE-44", - "text": "URL and not on the support portal of some other customer.\\n* Customer admin isn't able to see all the tickets of the organization.\\n\\n + This could happen if the customer isn't logged in on the correct URL. If the customer is logged in on the correct URL, then check if there are any tickets that are reported by the other customers in that organization or not. Check if the customer is added as a customer admin or not by logging in to your DevRev application.\\n* You are not able to add customer", - "title": "Customer portal | Computer for Support Teams | DevRev" + "id": "ART-4271_KNOWLEDGE_NODE-24", + "text": "[Support](/docs/product/support?)\\n 4. [Conversations](/docs/product/conversation?)\\n 5. [Convert Conversations to Tickets](/docs/product/Conversation-Tickets?)\\n\\n# Convert Conversations to Tickets\\n\\nYou can now convert conversations from PLuG and Slack directly into tickets. Previously, conversations were only linked to tickets. This update streamlines workflows and enhances the customer experience.\\n\\nFor conversations originating from PLuG or Slack, the **Link to Ticket** functionality", + "title": "Convert Conversations to Tickets | Conversations | Support | DevRev" }, { - "id": "ART-1953_KNOWLEDGE_NODE-36", - "text": "conversation](#ticket-linked-to-a-conversation)\\n* [Change of stage of a ticket/conversation](#change-of-stage-of-a-ticketconversation)\\n* [CSAT survey for conversation/ticket](#csat-survey-for-conversationticket)\\n* [Auto customer reply](#auto-customer-reply)\\n* [Auto reply on email](#auto-reply-on-email)\\n\\n[Enterprise grade security to protect customer data\\n\\nLearn more about it.\\n\\n![]()](/blog/soc-compliance)\\n\\nComputer\\n\\n* [Meet Computer](/meet-computer)\\n* [How Computer", - "title": "Customer email notifications | Computer by DevRev | DevRev" + "id": "ART-1645_KNOWLEDGE_NODE-5", + "text": "organization\\xe2\\x80\\x99s unique workflows and reporting needs. By using the customization framework, you can extend these objects with custom fields that reflect your processes.\\n\\nThis section provides an overview of the customization framework and walks you through the process of tracking bugs in your organization. By the end of this section, you\\xe2\\x80\\x99ll be able to:\\n\\n 1. Customize DevRev objects such as _issue_ and _ticket_ by adding custom fields.\\n 2. Override default field", + "title": "Object customization (Beta) \u2014 DevRev | Docs" }, { - "id": "ART-1953_KNOWLEDGE_NODE-24", - "text": "conversation](#reply-to-the-customer-on-a-conversation)\\n* [Reply to the customer on a ticket](#reply-to-the-customer-on-a-ticket)\\n* [Ticket linked to a conversation](#ticket-linked-to-a-conversation)\\n* [Change of stage of a ticket/conversation](#change-of-stage-of-a-ticketconversation)\\n* [CSAT survey for conversation/ticket](#csat-survey-for-conversationticket)\\n* [Auto customer reply](#auto-customer-reply)\\n* [Auto reply on email](#auto-reply-on-email)\\n\\n1. [Documentation](/docs)\\n3.", - "title": "Customer email notifications | Computer by DevRev | DevRev" + "id": "ART-3208_KNOWLEDGE_NODE-25", + "text": "the target organization. Those marked as **Supported** are eligible for import.\\n\\n| DevRev Object | Sync to DevRev |\\n| --- | --- |\\n| Issue | \\xe2\\x9c\\x85 |\\n| Ticket | \\xe2\\x9c\\x85 |\\n| DevUser | \\xe2\\x9c\\x85 |\\n| Customer | \\xe2\\x9c\\x85 |\\n| Tag | \\xe2\\x9c\\x85 |\\n| Product | \\xe2\\x9c\\x85 |\\n| Capability | \\xe2\\x9c\\x85 |\\n| Enhancement | \\xe2\\x9c\\x85 |\\n| Feature | \\xe2\\x9c\\x85 |\\n| Runnable | \\xe2\\x9c\\x85 |\\n| Links on works | \\xe2\\x9c\\x85 |\\n| Timeline Comment | \\xe2\\x9c\\x85 |\\n| Account |", + "title": "DevRev AirSync | AirSync | Snap-ins | DevRev" }, { - "id": "ART-1953_KNOWLEDGE_NODE-31", - "text": "stage of a ticket/conversation\\n----------------------------------------\\n\\n* **Trigger**: When there\\'s a change of stage in a ticket or conversation.\\n* **Action**: The system sends out a notification detailing the Ticket/Conversation number and stage change.\\n* **Sender**: {Company\\\\_Name} [support@yourdomain.com](mailto:support@yourdomain.com)\\n* **Subject**:\\n + For ticket: \"[{Company\\\\_Name}] Update on TKT-XXX - Ticket Title\"\"\"\\n + For conversations:", - "title": "Customer email notifications | Computer by DevRev | DevRev" + "id": "ART-4271_KNOWLEDGE_NODE-29", + "text": "end user.\\n\\n## Why you should convert a Conversation to a Ticket\\n\\nConsider converting a conversation to a ticket in these scenarios:\\n\\n * **Complex issues** : When a customer inquiry requires in-depth investigation that can't be resolved in a quick conversation.\\n * **Cross-team collaboration** : Issues requiring input from multiple departments or specialists.\\n * **Escalation needs** : When a conversation needs to be escalated to a higher support tier.\\n * **Feature requests** :", + "title": "Convert Conversations to Tickets | Conversations | Support | DevRev" } ] }, @@ -60,54 +60,54 @@ "query": "Android SDK session generated with Unknown user", "retrievals": [ { - "id": "ART-2898_KNOWLEDGE_NODE-10", - "text": "identification\\n\\nThe anonymous identification method allows you to create an anonymous user with an optional or random user identifier, ensuring that no other data is stored or associated with the user.\\n\\n###### Kotlin\\n\\n###### Java\\n\\n[code]\\n\\n 1| DevRev.identifyAnonymousUser( \\n ---|--- \\n 2| userId: String \\n 3| )\\n[/code] \\n \\n### Unverified identification\\n\\nThe unverified identification method identifies users with a unique identifier, but it does not verify their", - "title": "Android integration \u2014 DevRev | Docs" - }, - { - "id": "ART-15513_KNOWLEDGE_NODE-1", - "text": "[Exchange your AAT for a session token](/sdks/android/features#exchange-your-aat-for-a-session-token)\\n* [Identify the verified user](/sdks/android/features#identify-the-verified-user)\\n* [Updating the user](/sdks/android/features#updating-the-user)\\n* [Logout](/sdks/android/features#logout)\\n* [Identity model](/sdks/android/features#identity-model)\\n* [Properties](/sdks/android/features#properties)\\n* [User traits](/sdks/android/features#user-traits)\\n* [Organization", + "id": "ART-15513_KNOWLEDGE_NODE-0", + "text": "b'Features | DevRev | Docs\\n\\n[![]()![]()](https://developer.devrev.ai/)\\n\\nPublic\\n\\nPublic\\n\\nSearch\\n\\n`/`\\n\\nOn this page\\n\\n* [Identification](/sdks/android/features#identification)\\n* [Identify an anonymous user](/sdks/android/features#identify-an-anonymous-user)\\n* [Identify an unverified user](/sdks/android/features#identify-an-unverified-user)\\n* [Identify a verified user](/sdks/android/features#identify-a-verified-user)\\n* [Generate an AAT](/sdks/android/features#generate-an-aat)\\n*", "title": "Features | DevRev | Docs" }, { "id": "ART-2898_KNOWLEDGE_NODE-1", - "text": "identification](/public/sdks/mobile/android#unverified-identification)\\n * [Update user information](/public/sdks/mobile/android#update-user-information)\\n * [PLuG support chat](/public/sdks/mobile/android#plug-support-chat)\\n * [Analytics](/public/sdks/mobile/android#analytics)\\n * [Session analytics](/public/sdks/mobile/android#session-analytics)\\n * [Opt in or out](/public/sdks/mobile/android#opt-in-or-out)\\n * [Session recording](/public/sdks/mobile/android#session-recording)\\n *", + "text": "identification](/public/sdks/mobile/android#unverified-identification)\\n * [Update user information](/public/sdks/mobile/android#update-user-information)\\n * [PLuG support chat](/public/sdks/mobile/android#plug-support-chat)\\n * [Analytics](/public/sdks/mobile/android#analytics)\\n * [Session analytics](/public/sdks/mobile/android#session-analytics)\\n * [Opt in or out](/public/sdks/mobile/android#opt-in-or-out)\\n * [Session recording](/public/sdks/mobile/android#session-recording)\\n *", "title": "Android integration \u2014 DevRev | Docs" }, { - "id": "ART-15506_KNOWLEDGE_NODE-29", - "text": "window.plugSDK.shutdown(); |\\n| 6 | } |\\n| 7 | window.plugSDK.init({ |\\n| 8 | app_id: appId, |\\n| 9 | |\\n| 10 | // Pass the session details |\\n| 11 | session_recording_options: { |\\n| 12 | sessionDetails: { |\\n| 13 | sessionId: sessionId, |\\n| 14 | tabId: tabId, |\\n| 15 | }, |\\n| 16 | }, |\\n| 17 | |\\n| 18 | // With session token |\\n| 19 | session_token: sessionToken, |\\n| 20 | // Or without session token |\\n| 21 | identity: {}, |\\n| 22 | }); |\\n```\\n\\nWas this page", - "title": "Identify your users with Plug | DevRev | Docs" + "id": "ART-2982_KNOWLEDGE_NODE-7", + "text": "SDK will automatically create an anonymous user for you immediately after the SDK is configured.\\n\\n#####\\n\\nThe `Identity` structure allows for custom fields in the user, organization, and account traits. These fields must be configured through the DevRev app before they can be utilized. For more information, refer to [Object customization](https://devrev.ai/docs/product/object-customization).\\n\\nYou can select from the following methods to identify users within your application:\\n\\n###", + "title": "React Native integration \u2014 DevRev | Docs" }, { - "id": "ART-4255_KNOWLEDGE_NODE-10", - "text": "DevRev.identifyAnonymousUser( \\n ---|--- \\n 2| userId: String \\n 3| )\\n[/code] \\n \\n### Unverified identification\\n\\nThe unverified identification method identifies users with a unique identifier, but it does not verify their identity with the DevRev backend.\\n\\n###### Kotlin\\n\\n###### Java\\n\\n[code]\\n\\n 1| DevRev.identifyUnverifiedUser( \\n ---|--- \\n 2| identity: Identity \\n 3| )\\n[/code] \\n \\nThe function accepts the `Identity` object, where the user", - "title": "DevRev SDK for Android \u2014 DevRev | Docs" + "id": "ART-12475_KNOWLEDGE_NODE-1", + "text": ".\\n\\nProceed to integrate the DevRev PLuG SDK. For specific platform migration guides, refer to the following resources:\\n\\nAndroid SDK migration guide: Android Migration Guide\\n\\niOS SDK migration guide: iOS Migration Guide\\n\\nReact Native & Expo SDK migration guide: React Native Migration Guide\\n\\nCordova SDK migration guide: Cordova Migration Guide\\n\\nWeb SDK migration guide: Web Migration Guide\\n\\nOnce the integration is complete, you will be able to view sessions on the Session", + "title": "Migrating from UserExperior to DevRev" }, { - "id": "ART-15506_KNOWLEDGE_NODE-4", - "text": "RevUser Session Token(5) Return Session Token(6) Call plugSDK.init() with token\\n\\nGenerate an application access token\\n------------------------------------\\n\\n1. In DevRev, go to **Settings > Support > Plug Tokens** through the settings icon on the top-left corner.\\n2. Under the **Application access tokens** panel, click **New token** and copy the token that\\xe2\\x80\\x99s displayed.\\n\\n##### \\n\\nEnsure you copy your access token, as you cannot view it again.\\n\\nGenerate a session", - "title": "Identify your users with Plug | DevRev | Docs" + "id": "ART-15513_KNOWLEDGE_NODE-1", + "text": "[Exchange your AAT for a session token](/sdks/android/features#exchange-your-aat-for-a-session-token)\\n* [Identify the verified user](/sdks/android/features#identify-the-verified-user)\\n* [Updating the user](/sdks/android/features#updating-the-user)\\n* [Logout](/sdks/android/features#logout)\\n* [Identity model](/sdks/android/features#identity-model)\\n* [Properties](/sdks/android/features#properties)\\n* [User traits](/sdks/android/features#user-traits)\\n* [Organization", + "title": "Features | DevRev | Docs" }, { - "id": "ART-4255_KNOWLEDGE_NODE-1", - "text": "information](/public/sdks/android#update-user-information)\\n * [PLuG support chat](/public/sdks/android#plug-support-chat)\\n * [Analytics](/public/sdks/android#analytics)\\n * [Session analytics](/public/sdks/android#session-analytics)\\n * [Opt in or out](/public/sdks/android#opt-in-or-out)\\n * [Session recording](/public/sdks/android#session-recording)\\n * [Session properties](/public/sdks/android#session-properties)\\n * [Timers](/public/sdks/android#timers)\\n * [Screen", - "title": "DevRev SDK for Android \u2014 DevRev | Docs" + "id": "ART-15515_KNOWLEDGE_NODE-5", + "text": "page\\n\\nIdentification\\n--------------\\n\\nTo access certain features of the DevRev SDK, user identification is required.\\n\\nThe identification function should be placed appropriately in your app after the user logs in. If you have the user information available at app launch, call the function after the `DevRev.configure(appID:)` method.\\n\\n##### \\n\\nIf you haven\\xe2\\x80\\x99t previously identified the user, the DevRev SDK will automatically create an anonymous user for you immediately after the", + "title": "Features | DevRev | Docs" }, { - "id": "ART-4255_KNOWLEDGE_NODE-33", - "text": "\\n**Solution** : Confirm that user identification is performed before using the `showSupport()` function or XML button.\\n\\n * **Issue** : Incorrect operation due to `App ID` and `secret` misconfiguration. \\n**Solution** : Ensure correct functionality by double-checking that both `App ID` and `secret` values are accurately configured in your application or sample app.\\n\\nWas this page helpful?YesNo\\n\\n[DevRev SDK for iOSUp Next](/public/sdks/ios)\\n\\n[Built", - "title": "DevRev SDK for Android \u2014 DevRev | Docs" + "id": "ART-12449_KNOWLEDGE_NODE-2", + "text": "identification](/public/sdks/android/features#verified-identification)\\n * [Updating the user](/public/sdks/android/features#updating-the-user)\\n * [Logout](/public/sdks/android/features#logout)\\n * [PLuG support chat](/public/sdks/android/features#plug-support-chat)\\n * [Creating a new conversation](/public/sdks/android/features#creating-a-new-conversation)\\n * [In-app link handling](/public/sdks/android/features#in-app-link-handling)\\n *", + "title": "Features \u2014 DevRev | Docs" }, { - "id": "ART-4255_KNOWLEDGE_NODE-8", - "text": "Identification\\n\\nTo use certain features of the DevRev SDK, user identification is required. You can select from the following methods to identify users within your application:\\n\\n#####\\n\\nThe identification function should be placed appropriately in your app after the user logs in. If you have the user information available at app launch, call the function after the `DevRev.configure(context, appID)` method.\\n\\n#####\\n\\nThe `Identity` structure allows for custom fields in the user,", - "title": "DevRev SDK for Android \u2014 DevRev | Docs" + "id": "ART-2665_KNOWLEDGE_NODE-25", + "text": "specified, the default options are used.\\n\\nPlug SDK offers the ability to hide sensitive user information by masking it in session recordings. During session replays, masking replaces user-visible or typed content in specific elements with asterisks (\"\\\\*\"). This ensures that sensitive information is not displayed in the recordings, protecting user privacy.\\n\\nDuring Plug initialization, you have several options to manually configure which elements should be masked. Masking is applied based on", + "title": "Session recording options | Session analytics | Computer for Your Customers | DevRev" }, { - "id": "ART-2898_KNOWLEDGE_NODE-9", - "text": "in your app after the user logs in. If you have the user information available at app launch, call the function after the `DevRev.configure(context, appID)` method.\\n\\n#####\\n\\nThe `Identity` structure allows for custom fields in the user, organization, and account traits. These fields must be configured through the DevRev app before they can be utilized. For more information, refer to [Object customization](https://devrev.ai/docs/product/object-customization).\\n\\n### Anonymous", - "title": "Android integration \u2014 DevRev | Docs" + "id": "ART-15510_KNOWLEDGE_NODE-4", + "text": "features of the DevRev SDK, user identification is required.\\n\\nThe identification function should be placed appropriately in your app after the user logs in. If you have the user information available at app launch, call the function after the `DevRev.configure(appID)` method.\\n\\n##### \\n\\nOn iOS, if you haven\\xe2\\x80\\x99t previously identified the user, the DevRev SDK will automatically create an anonymous user for you immediately after the SDK is configured.\\n\\n##### \\n\\nThe `Identity`", + "title": "Features | DevRev | Docs" + }, + { + "id": "ART-15792_KNOWLEDGE_NODE-13", + "text": "on data\\n\\nLight-weight SDK: Collect session recordings without affecting speed\\n\\nSource: [DevRev User Observability](https://devrev.ai/plug-observability)'", + "title": "DevRev Products and Agents" } ] }, @@ -121,49 +121,49 @@ "title": "Customer email notifications | Computer by DevRev | DevRev" }, { - "id": "ART-1979_KNOWLEDGE_NODE-36", - "text": "contact](https://docs.devrev.ai/product/plug) must be created first for any emails to be added as subscribers.\\n* **Needs response**: Set to true whenever a new customer message is received on the ticket to ensure that no customer messages are missed. If a particular customer message does not need a response, the **Needs response** toggle can be turned off by the user. Turning off the **Needs response** toggle does not affect the SLA metrics.\\n\\nThese attributes can be effectively used in", - "title": "Tickets | Computer for Support Teams | DevRev" - }, - { - "id": "ART-1986_KNOWLEDGE_NODE-37", - "text": "a customer * The ticket was created by a customer experience engineer but reported by a customer | A new comment on the ticket by the customer after the customer experience engineer replied | * The agent added a comment to the customer chat * The ticket is moved to Awaiting Customer Response, or the ticket is closed | | |\\n| Full resolution time | * Ticket created by a customer * The ticket was created by a customer experience engineer but reported by a customer | Ticket created | The", - "title": "Service-level agreement | Computer for Support Teams | DevRev" + "id": "ART-1978_KNOWLEDGE_NODE-43", + "text": "with that email or not.\\n + This could also be because your customer hasn't logged in.\\n* Customer isn't able to view the tickets they have created.\\n\\n + Check if there are any reported tickets by that customer. You can do so by logging into your DevRev app and then going into the tickets section. Here you can filter based on **reported by** and see if any tickets have been reported by the customer who isn't able to view the tickets.\\n + Check if the customer has logged in on the correct", + "title": "Customer portal | Computer for Support Teams | DevRev" }, { - "id": "ART-1979_KNOWLEDGE_NODE-61", - "text": "following scenarios can lead to the creation of follow up ticket:\\n\\n* Customers communicated on an archived/immutable ticket from any channel such as email.\\n* Customer communicated on a merged ticket and the primary ticket is also archived.\\n\\nAfter creation of a follow up ticket the customer messages will reflect only on the new followup ticket and the customer will continue to see response on the same thread in channels like email & slack. The user can continue responding on the new follow", - "title": "Tickets | Computer for Support Teams | DevRev" + "id": "ART-2027_KNOWLEDGE_NODE-36", + "text": "Receives Replies From | Thread is visible in portal |\\n| --- | --- | --- | --- |\\n| Email to support | [support@yourcompany.com](mailto:support@yourcompany.com) | [support@yourcompany.com](mailto:support@yourcompany.com) | Yes |\\n| Ticket via Customer Portal or Plug widget (Channel on ticket = Plug or Portal) | Ticket form on Customer Portal or conversation converted to ticket from Plug widget | - If Channel is set as email in the config, replies are sent via the configured email address. -", + "title": "Email | Integrate | Snap-ins | DevRev" }, { - "id": "ART-1953_KNOWLEDGE_NODE-5", - "text": "ticket conversion](/docs/product/conversation-ticket)\\n + [Tickets](/docs/product/tickets)\\n + [Routing](/docs/product/routing)\\n + [Support best practices](/docs/product/support-bp)\\n + [Customer portal](/docs/product/support-portal)\\n + [Questions & answers](/docs/product/qa)\\n + [Knowledge Base](/docs/product/knowledge-base)\\n\\n - [Articles](/docs/product/articles)\\n - [Collections](/docs/product/collection)\\n + [Turing AI agent](/docs/product/conversational-bot)\\n\\n - [Best", - "title": "Customer email notifications | Computer by DevRev | DevRev" + "id": "ART-2027_KNOWLEDGE_NODE-43", + "text": "recipients in the **To** or **Cc**\\n\\nThreading\\n---------\\n\\nEmail integration preserves threading by using the **References** and **In-Reply-To** email headers and by correlating the email **Subject** field and the ticket title. If either the ticket title or the email subject is changed at any point after ticket creation, follow up emails may cause a new ticket to be created.\\n\\n![]()\\n\\nOnce a ticket is created from an email, it is recommended to avoid changing the email subject or the", + "title": "Email | Integrate | Snap-ins | DevRev" }, { - "id": "ART-2027_KNOWLEDGE_NODE-36", - "text": "Receives Replies From | Thread is visible in portal |\\n| --- | --- | --- | --- |\\n| Email to support | [support@yourcompany.com](mailto:support@yourcompany.com) | [support@yourcompany.com](mailto:support@yourcompany.com) | Yes |\\n| Ticket via Customer Portal or Plug widget (Channel on ticket = Plug or Portal) | Ticket form on Customer Portal or conversation converted to ticket from Plug widget | - If Channel is set as email in the config, replies are sent via the configured email address. -", + "id": "ART-2027_KNOWLEDGE_NODE-37", + "text": "If Channel is not email, it is sent from the email address configured in the snap-in under **Notification sender email address**. - If no email snap-in is installed, the reply is sent from [notifications@devrev.ai](mailto:notifications@devrev.ai). | Yes |\\n| Replies to notification emails | Email reply | Response added to ticket thread | Yes |\\n\\n![]()\\n\\nEven when a reply comes via email, it\\xe2\\x80\\x99s always synced into the customer\\xe2\\x80\\x99s portal view.\\n\\nEmail experience from an", "title": "Email | Integrate | Snap-ins | DevRev" }, { - "id": "ART-1953_KNOWLEDGE_NODE-24", - "text": "conversation](#reply-to-the-customer-on-a-conversation)\\n* [Reply to the customer on a ticket](#reply-to-the-customer-on-a-ticket)\\n* [Ticket linked to a conversation](#ticket-linked-to-a-conversation)\\n* [Change of stage of a ticket/conversation](#change-of-stage-of-a-ticketconversation)\\n* [CSAT survey for conversation/ticket](#csat-survey-for-conversationticket)\\n* [Auto customer reply](#auto-customer-reply)\\n* [Auto reply on email](#auto-reply-on-email)\\n\\n1. [Documentation](/docs)\\n3.", - "title": "Customer email notifications | Computer by DevRev | DevRev" + "id": "ART-3207_KNOWLEDGE_NODE-38", + "text": "Step 2: Define the Primary Use Case\\n\\nChoose how DevRev should interpret emails sent to the primary address:\\n\\n* Choose between generating a **Ticket or a Conversation** from the incoming email.\\n\\nToggle on **Set email as the default channel for tickets** to ensure that:\\n\\n* Customer chat replies are sent via email as well as to the original source of the channel.\\n\\n### Step 3: Add Additional Support Emails\\n\\nYou can add more addresses to handle support requests.\\n\\n* **Tickets**: Emails", + "title": "Email snap-in configuration | Email | Integrate | Snap-ins | DevRev" }, { - "id": "ART-1979_KNOWLEDGE_NODE-52", - "text": "don\\xe2\\x80\\x99t forget to give \\xf0\\x9f\\x91\\x8d on the suggestion if you like it or \\xf0\\x9f\\x91\\x8e to dislike it.\\n\\n![]()\\n\\nDuplicate ticket merging\\n------------------------\\n\\nDuplicate tickets in a support system pose a significant challenge by creating inefficiencies, increasing the workload for support agents, and negatively impacting user experience. These tickets often result from user frustration or misunderstandings of the resolution process, leading to confusion and disrupting", - "title": "Tickets | Computer for Support Teams | DevRev" + "id": "ART-2027_KNOWLEDGE_NODE-29", + "text": "your communication requirements.\\n\\nThe visibility and interaction capabilities with a ticket in DevRev are determined by the user's role and how they were added to the email thread.\\n\\nEnd users\\n\\n* Original sender\\n\\n *Added to:* **Reported by** or **Email members** field.\\n\\n *Is able to:* View the ticket on the portal and reply via email.\\n* An end user in the same organization\\n\\n *Added to:* **To** or **CC** fields in the email thread; **Reported by** field, **Email members** field,", + "title": "Email | Integrate | Snap-ins | DevRev" }, { - "id": "ART-1953_KNOWLEDGE_NODE-35", - "text": "installed [Auto-reply snap-in](https://docs.devrev.ai/automations/auto-reply).\\n\\n[PreviousUpdates](/docs/product/updates)[NextRoles](/docs/product/roles)\\n\\n#### On this page\\n\\n* [White-label customer email notifications](#whitelabel-customer-email-notifications)\\n* [Reply to the customer on a conversation](#reply-to-the-customer-on-a-conversation)\\n* [Reply to the customer on a ticket](#reply-to-the-customer-on-a-ticket)\\n* [Ticket linked to a", + "id": "ART-1953_KNOWLEDGE_NODE-30", + "text": "linked to a conversation\\n-------------------------------\\n\\n* **Trigger**: A ticket is linked to an existing conversation.\\n* **Action**: The system sends out a notification with the linked ticket number.\\n* **Sender**: {Company\\\\_Name} [support@yourdomain.com](mailto:support@yourdomain.com)\\n* **Subject**: \"\"\\n\\n![]()\\n\\nThis email is only sent to the organizations with [Convergence snap-in](https://docs.devrev.ai/automations/converge)\\n\\nChange of", "title": "Customer email notifications | Computer by DevRev | DevRev" }, { - "id": "ART-1979_KNOWLEDGE_NODE-47", - "text": "validate the fix with the user and then to *resolved*. If the user wants to cancel the ticket then the stage moves to *canceled*.\\n\\n**Closed**\\n\\n* *Canceled* (C)\\n\\n The ticket is determined to be invalid either by the user or the customer experience engineer. In certain scenarios, a ticket may have been created by accident and may be canceled by the creator. In other scenarios, garbage tickets may be created through automation or because of spam. Automation or the customer experience", - "title": "Tickets | Computer for Support Teams | DevRev" + "id": "ART-2027_KNOWLEDGE_NODE-28", + "text": "email address that messages to it create either a conversation or a ticket, but not both simultaneously. Whether to create a conversation or a ticket depends on the nature of the emails received at a specific email address.\\n\\nRead more about [conversations](../product/conversation) and [tickets](../product/tickets) to decide which is more suitable for your use case.\\n\\nWhen needed, you can link a conversation to a ticket. This is particularly useful if you decide to use conversations for all", + "title": "Email | Integrate | Snap-ins | DevRev" + }, + { + "id": "ART-3235_KNOWLEDGE_NODE-24", + "text": "[Snap-ins](/docs/snapins)\\n[Automate](/docs/automate)\\n[Reported by enricher](/docs/automations/ticket-reported-by)\\n\\nReported by enricher\\n====================\\n\\nThe [Reported by Enricher](https://marketplace.devrev.ai/ticket-reported-by) snap-in automatically updates the **Reported By** field on tickets created with an email entered in a custom field. It verifies if the email belongs to an existing customer of the configured account and either links to that customer or creates a new", + "title": "Reported by enricher | Automate | Snap-ins | DevRev" } ] }, @@ -172,54 +172,54 @@ "query": "manage access and privileges in DevRev", "retrievals": [ { - "id": "ART-1958_KNOWLEDGE_NODE-24", - "text": "policies](#mfz-policies)\\n* [Sharing](#sharing)\\n* [Vista privileges](#vista-privileges)\\n\\n1. [Documentation](/docs)\\n3. [Computer by DevRev](/docs/intro)\\n[Access control](/docs/product/access-control)\\n\\nAccess control\\n==============\\n\\nAccess control in DevRev is a system that authorizes an actor to perform actions on different targets within the application. In this context, an actor is any entity that interacts with the app, such as an organization member, a customer, a system user, or a", - "title": "Access control | Computer by DevRev | DevRev" + "id": "ART-1948_KNOWLEDGE_NODE-31", + "text": "can configure what access a certain group has, by assigning and revoking roles for a group.\\n\\n1. To assign/revoke roles for a group, go to [**User Management > Groups**](https://app.devrev.ai/devrev/settings/groups), and click the group in which you want to make changes.\\n2. Click the **Privileges** tab and select your target object or category (Support, Build, Grow, Analytics).\\n\\n**Currently, available targets are:**\\n\\n* Ticket\\n* Issue\\n* Opportunity\\n* Account\\n* Workspaces\\n*", + "title": "Groups | Computer by DevRev | DevRev" }, { - "id": "ART-1955_KNOWLEDGE_NODE-46", - "text": "admins on revus.\\n\\n Privileges: revu object ['CREATE', 'READ', 'UPDATE', 'DELETE']\\n* *devo Admin:* Contains privileges for admins on devos.\\n\\n Privileges: devo object ['CREATE', 'READ', 'UPDATE', 'DELETE']\\n* *flow Admin:* Contains privileges for admins on flows.\\n\\n Privileges: flow object ['CREATE', 'READ', 'UPDATE', 'DELETE']\\n* *webhook Admin:* Contains privileges for admins on webhooks.\\n\\n Privileges: webhook object ['CREATE', 'READ', 'UPDATE', 'DELETE']\\n* *product Admin:*", - "title": "Default privileges by group | Roles | Computer by DevRev | DevRev" + "id": "ART-1966_KNOWLEDGE_NODE-31", + "text": "\"DevRev\" that you created earlier under Enterprise applications. Within the application, go to **Users and Groups** and assign the users who can access the app.\\n\\nConfigure DevRev to use your identity provider\\n----------------------------------------------\\n\\nAfter registering DevRev as an application in your identity provider, you need to create an authentication connection in DevRev that links to your identity provider. This connection enables DevRev to authenticate users through your", + "title": "External identity provider setup | Computer by DevRev | DevRev" }, { - "id": "ART-1963_KNOWLEDGE_NODE-1", - "text": "[Groups](/docs/product/groups)\\n + [Parts & trails](/docs/product/parts)\\n + [Vistas](/docs/product/vistas)\\n\\n - [Vista Reports](/docs/product/vista-reports)\\n - [Board view](/docs/product/board-view)\\n + [Tasks](/docs/product/tasks)\\n + [Updates](/docs/product/updates)\\n + [Customer email notifications](/docs/product/customer-emails)\\n + [Roles](/docs/product/roles)\\n\\n - [Default privileges by group](/docs/product/privs)\\n + [Access control](/docs/product/access-control)\\n +", - "title": "Accessing DevRev | Computer by DevRev | DevRev" + "id": "ART-1955_KNOWLEDGE_NODE-0", + "text": "b\"Default privileges by group | Roles | Computer by DevRev | DevRev\\n\\n* Computer\\n* Resources\\n* [Our Customers](/case-study)\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](/request-a-demo)\\n\\nComputer\\n\\nResources\\n\\n[Our Customers](/case-study)\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](/request-a-demo)\\n\\nSearch\\n\\n`CTRL`\\xc2\\xa0+\\xc2\\xa0`K`\\n\\n* [Introduction](/docs)\\n* [Computer by DevRev](/docs/intro)\\n\\n + [Core concepts](/docs/product/core)\\n +", + "title": "Default privileges by group | Roles | Computer by DevRev | DevRev" }, { - "id": "ART-1958_KNOWLEDGE_NODE-23", - "text": "2025](/docs/changelog/_2025-06-01)\\n + [May 2025](/docs/changelog/_2025-05-01)\\n + [March and April 2025](/docs/changelog/_2025-04-01)\\n + [February 2025](/docs/changelog/_2025-02-01)\\n* [Developer \\xe2\\x86\\x97\\xef\\xb8\\x8f](https://developer.devrev.ai/)\\n* [DevRevU \\xe2\\x86\\x97\\xef\\xb8\\x8f](/docs/DevRevU)\\n\\n + [Product demos](/docs/DevRevU/demos)\\n\\nOn this page\\n\\n* [Privilege determination](#privilege-determination)\\n* [Granting access permissions](#granting-access-permissions)\\n* [MFZ", - "title": "Access control | Computer by DevRev | DevRev" + "id": "ART-17233_KNOWLEDGE_NODE-8", + "text": "entry in the `shared_with` collection contains two key components:\\n\\n* `member_id`: Identifies which user or group is being granted access.\\n* `role`: Specifies the permission level (for example, \\xe2\\x80\\x9cviewer\\xe2\\x80\\x9d, \\xe2\\x80\\x9ceditor\\xe2\\x80\\x9d, \\xe2\\x80\\x9cowner\\xe2\\x80\\x9d). DevRev offers a set of predefined roles.\\n\\n### Member types\\n\\nThe `member_id` field can reference three different types of objects:\\n\\n* Individual users (`#record:users`)\\n* Standard groups", + "title": "Permissions | DevRev | Docs" }, { - "id": "ART-1955_KNOWLEDGE_NODE-66", - "text": "Privileges: devu object ['CREATE', 'READ', 'UPDATE', 'DELETE']\\n* *revu Admin:* Contains privileges for admins on revus.\\n\\n Privileges: revu object ['CREATE', 'READ', 'UPDATE', 'DELETE']\\n* *devo Admin:* Contains privileges for admins on devos.\\n\\n Privileges: devo object ['CREATE', 'READ', 'UPDATE', 'DELETE']\\n* *flow Admin:* Contains privileges for admins on flows.\\n\\n Privileges: flow object ['CREATE', 'READ', 'UPDATE', 'DELETE']\\n* *webhook Admin:* Contains privileges for admins on", - "title": "Default privileges by group | Roles | Computer by DevRev | DevRev" + "id": "ART-1472_KNOWLEDGE_NODE-29", + "text": "documentation](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens).\\n\\n#### Step 2: Add PAT to DevRev connections\\n\\nAdd the generated PAT as a snap-in secret in DevRev. This secret is used during the installation of the snap-in. Ensure that the secret is shared within the organization to allow the snap-in to access it.\\n\\n#### Step 3: Install the snap-in\\n\\nDuring the installation of the snap-in, utilize the shared secret to", + "title": "Using a snap-in to perform an external action \u2014 DevRev | Docs" }, { - "id": "ART-1955_KNOWLEDGE_NODE-93", - "text": "Teams](/for-support-teams)\\n* [For Builders](/for-builders)\\n* [For Customers](/for-customers)\\n* [For User Insights](/for-user-insights)\\n* [Marketplace](https://marketplace.devrev.ai/)\\n\\nResources\\n\\n* [Blog](/blog)\\n* [Our Customers](/case-study)\\n* [Snap-In Extensions](https://developer.devrev.ai/public/snapin-development/concepts)\\n* [DevRevU training](/docs/DevRevU)\\n* [Documentation](https://docs.devrev.ai/)\\n* [API References](https://docs.devrev.ai/api/)\\n\\nCompany\\n\\n*", - "title": "Default privileges by group | Roles | Computer by DevRev | DevRev" + "id": "ART-1966_KNOWLEDGE_NODE-42", + "text": "process from your identity provider\\'s portal. The latter is not supported on DevRev.\\n\\nA workaround for supporting IDP-initiated SSO is to bookmark your DevRev workspace URL (that is https://app.devrev.ai/) in your IDP. With only SSO Auth connection enabled, the experience would be as seamless as SP-initiated SSO.\\n\\n### Parameter reference\\n\\n* : Your Personal Access Token with admin permissions\\n* : Your DevRev organization ID (from the initial API", + "title": "External identity provider setup | Computer by DevRev | DevRev" }, { - "id": "ART-1955_KNOWLEDGE_NODE-29", - "text": "revUsers for revUsers to view there revUsers with same email.\\n\\n Privileges: revu object ['READ']\\n* *RevUser License Viewer:* A role that enables a user to view licenses assigned to them.\\n\\n Privileges: license\\\\_assignment object ['READ']\\n\\n\\xe2\\x80\\x9cPlatform Users\\xe2\\x80\\x9d group\\n----------------------\\n\\nGroup for all internal employees, includes default privileges to do common operations.\\n\\n**Privileges:**\\n\\n* *Devu Self Interactor:* Contains privileges on user for members of", - "title": "Default privileges by group | Roles | Computer by DevRev | DevRev" + "id": "ART-15511_KNOWLEDGE_NODE-10", + "text": "global user object. DevRev utilizes the `RevUser` object and `addSessionProperties()` for enhanced functionality.\\n\\nFor setting user properties, refer to the [User Identification](https://developer.devrev.ai/sdks/web/user-identity).\\n\\n###### UserExperior implementation\\n\\n###### Replace with Plug\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | ue.setUserProperties({ |\\n| 2 | key1: value1, |\\n| 3 | key2: value2, |\\n| 4 | ... |\\n| 5 | }) |\\n```\\n\\nRestart a session\\n-----------------\\n\\nTerminate the", + "title": "UserExperior migration | DevRev | Docs" }, { - "id": "ART-1955_KNOWLEDGE_NODE-87", - "text": "['CREATE', 'READ', 'UPDATE', 'DELETE']\\n* *credit revuser admin:* Contains workspace billing admin privileges for credit.\\n\\n Privileges: credit object ['CREATE', 'READ', 'UPDATE', 'DELETE']\\n* *RevOrg Billing Admin AccountCommerceDetails Manager:* Contains workspace billing admin privileges for accountCommerceDetails objects.\\n\\n Privileges: account\\\\_commerce\\\\_details object ['READ', 'UPDATE']\\n* *RevOrg Billing Admin License Assignment Manager:* Contains workspace billing admin privileges", - "title": "Default privileges by group | Roles | Computer by DevRev | DevRev" + "id": "ART-1170_KNOWLEDGE_NODE-5", + "text": "DevRev APIs on behalf of the corresponding dev user. The lifetime of a PAT is usually in days. The subject of the PAT is set to the corresponding dev users DON (for example, `don:identity:dvrv-us-1:devo/0:devu/30`).\\n\\nPersonal access token usage\\n---------------------------\\n\\nAuthentication to DevRev APIs requires a personal access token (PAT). A PAT is used to uniquely identify a dev user in context of a dev org and can be used by external third-party applications to access DevRev APIs on", + "title": "Authentication | DevRev | Docs" }, { - "id": "ART-1955_KNOWLEDGE_NODE-95", - "text": "Status](/status)\\n\\n\\xc2\\xa9 2025 DevRev Inc.\"", + "id": "ART-1955_KNOWLEDGE_NODE-66", + "text": "Privileges: devu object ['CREATE', 'READ', 'UPDATE', 'DELETE']\\n* *revu Admin:* Contains privileges for admins on revus.\\n\\n Privileges: revu object ['CREATE', 'READ', 'UPDATE', 'DELETE']\\n* *devo Admin:* Contains privileges for admins on devos.\\n\\n Privileges: devo object ['CREATE', 'READ', 'UPDATE', 'DELETE']\\n* *flow Admin:* Contains privileges for admins on flows.\\n\\n Privileges: flow object ['CREATE', 'READ', 'UPDATE', 'DELETE']\\n* *webhook Admin:* Contains privileges for admins on", "title": "Default privileges by group | Roles | Computer by DevRev | DevRev" }, { - "id": "ART-1955_KNOWLEDGE_NODE-55", - "text": "Contact Admin field access role\\n\\n Privileges: revu object None\\n* *Vista Creator:* A role that allows a user to create a vista\\n\\n Privileges: vista object ['CREATE']\\n* *Vista Owner:* A role that allows the creator to view, edit and delete a vista\\n\\n Privileges: vista object ['READ', 'UPDATE', 'DELETE']\\n* *Issue Admin Field Access:* Issue admin field access role\\n\\n Privileges: issue object None\\n* *Dashboard Admin:* A role that allows CRUDL operations to admins\\n\\n Privileges:", - "title": "Default privileges by group | Roles | Computer by DevRev | DevRev" + "id": "ART-17233_KNOWLEDGE_NODE-13", + "text": "and groups.\\n\\n##### \\n\\nOnly 1-way sync (from the external system to DevRev) is supported for authorization policy.\\n\\n### Object fields\\n\\nThe Authorization policy object supports the following fields:\\n\\n* `groups` (optional): A list of group identifiers from the external system to which this policy applies.\\n* `users` (optional): A list of user identifiers from the external system to which this policy applies.\\n* `targets`: Defines the DevRev record types the permissions apply to. It uses", + "title": "Permissions | DevRev | Docs" } ] }, @@ -228,54 +228,54 @@ "query": "SSO setup SAML IDP metadata connection string Google Workspace", "retrievals": [ { - "id": "ART-1966_KNOWLEDGE_NODE-39", - "text": "authentication methods to enforce SSO-only login. This is commonly done to ensure all users authenticate through your organization\\'s identity provider.\\n\\n**Common scenario**: If users were previously logging in with Google OAuth and you\\'ve now enabled SSO, you can disable Google authentication to force all users to use SSO.\\n\\nFirst, get the Google OAuth connection ID:\\n\\n```\\n```\\n1 curl --location --request GET \\'https://api.devrev.ai/dev-orgs.auth-connections.list\\' \\\\\\n\\n\\n\\n2 --header", - "title": "External identity provider setup | Computer by DevRev | DevRev" + "id": "ART-16086_KNOWLEDGE_NODE-6", + "text": "bases\\n\\n8. Conclusion\\n\\nThe SSO Setup Agent offers a fully guided, interactive setup for configuring SSO, with support for both SAML and OIDC. It includes validation, previews, and uses workflow-based skills to automate the process with minimal user intervention.'", + "title": "Single Sign On Configuration 3P Node" }, { - "id": "ART-1005_KNOWLEDGE_NODE-13", - "text": "model\\n\\n\\nWhat did we choose?\\nGoogle Workspace (Gsuite)\\n\\nWhy did we choose this?\\nAs mentioned in the IdP section above, I\\xe2\\x80\\x99ve worked a lot with Exchange, Sharepoint, and other Microsoft products and I like the simplicity of the Google Workspace solution. Does it have all of the features of Microsoft 360? No, but it gives us enough of what we need and integrates beautifully with Okta. If we had gone Azure AD on the IdP front, that obviously would have impacted this choice.\\n\\nWhat", - "title": "Choosing the Right Systems For Your Startup" + "id": "ART-15701_KNOWLEDGE_NODE-16", + "text": "created\\n\\nEnter the SSO URL in case you have configured SAML login as identity management in amazon connect instance.\\n\\nEnter the complete S3 Bucket names and path for call recording and transcript. The complete bucket names and path can be found here. Copy the complete path directly.\\n\\nSelect Invite All checkbox if you would like to invite all the support agents to DevRev workspace if not present.\\n\\nClick on install snap-in.\\n\\nAfter the snap-in status shows Active, go to the configured", + "title": "Amazon Connect Telephony Integration Guide" }, { - "id": "ART-1966_KNOWLEDGE_NODE-29", - "text": "are some common examples:\\n\\nAzure ADGoogle WorkspaceJump CloudOkta\\n\\n1. Log in to Azure Active Directory and select **Enterprise applications > + New application**.\\n2. Search for \"Azure AD SAML Toolkit\" in the **Browse Azure AD Gallery** and select it.\\n3. Enter DevRev as the name and click **Create**.\\n4. Select **Single sign-on > SAML**.\\n5. Edit the **Basic SAML Configuration** and enter the following parameters.\\n\\n * **Identifier** (Entity ID):", - "title": "External identity provider setup | Computer by DevRev | DevRev" + "id": "ART-16086_KNOWLEDGE_NODE-2", + "text": "and back-and-forth coordination The absence of a guided experience adds unnecessary friction to an otherwise smooth onboarding process. The proposed agentic skill aims to eliminate these barriers with a step-by-step SSO setup flow embedded directly within DevRev.\\n\\n3.System Specifications\\n\\nSupports both SAML and OIDC connection types.\\n\\nInteractive, step-by-step setup via agent conversation.\\n\\nCollects essential inputs from the user based on the selected connection type:-For SAML: sign-in", + "title": "Single Sign On Configuration 3P Node" }, { - "id": "ART-1966_KNOWLEDGE_NODE-20", - "text": "Datacenter AirSync](/docs/integrations/confluence-datacenter)\\n - [Google Docs](/docs/integrations/google-doc)\\n - [Google Drive](/docs/integrations/google-drive)\\n - [Gmail AirSync](/docs/integrations/gmail-airdrop)\\n - [Monday.com AirSync](/docs/integrations/monday)\\n - [Intercom AirSync](/docs/integrations/intercom)\\n - [Figma AirSync](/docs/integrations/figma-airdrop)\\n - [ServiceNow AirSync](/docs/integrations/servicenow)\\n - [ServiceNow KB", + "id": "ART-1966_KNOWLEDGE_NODE-26", + "text": "setup](/docs/product/sso-saml)\\n\\nExternal identity provider setup\\n================================\\n\\nDevRev can be configured to use external identity providers for SSO.\\n\\n![]()\\n\\nIf you want DevRev to use an external identity provider, follow the instructions for your organization\\xe2\\x80\\x99s provider.\\n\\nBefore you begin\\n----------------\\n\\nTo register DevRev as a SAML 2.0 application, you need the slug for your dev org.\\n\\nTo get the dev\\\\_oid and slug, run the following", "title": "External identity provider setup | Computer by DevRev | DevRev" }, { - "id": "ART-1966_KNOWLEDGE_NODE-35", - "text": "false,\\n\\n\\n\\n6 \"type\": \"samlp\",\\n\\n\\n\\n7 \"sign_in_endpoint\": \"\",\\n\\n\\n\\n8 \"connection_name\": \"\",\\n\\n\\n\\n9 }\\n\\n\\n\\n10 }\\n```\\n\\nShow more\\n```\\n\\nImportant\\n\\n* The connection\\\\_name must follow the naming pattern described earlier.\\n* Save the id field from the response\\xe2\\x80\\x94you need it for the next step.\\n* The connection is created with enabled: false by default for security.\\n\\n### Step 2: Enable the authentication connection\\n\\nAfter", - "title": "External identity provider setup | Computer by DevRev | DevRev" + "id": "ART-16616_KNOWLEDGE_NODE-31", + "text": "provider setup](/docs/product/sso-saml)[NextComputer for Support Teams](/docs/product/support)\\n\\n#### On this page\\n\\n* [Prerequisites](#prerequisites)\\n* [Authenticate with PAT](#authenticate-with-pat)\\n* [Configure for Claude desktop](#configure-for-claude-desktop)\\n* [Configure for Cursor](#configure-for-cursor)\\n\\n[Enterprise grade security to protect customer data\\n\\nLearn more about it.\\n\\n![]()](/blog/soc-compliance)\\n\\nComputer\\n\\n* [Meet Computer](/meet-computer)\\n* [How Computer", + "title": "Remote MCP server | Computer by DevRev | DevRev" }, { - "id": "ART-1966_KNOWLEDGE_NODE-34", - "text": "application/json\\' \\\\\\n\\n\\n\\n4 --data-raw \\'{\\n\\n\\n\\n5 \"type\": \"samlp\",\\n\\n\\n\\n6 \"sign_in_endpoint\": \"\",\\n\\n\\n\\n7 \"signing_cert\": \"\",\\n\\n\\n\\n8 \"connection_name\": \"\",\\n\\n\\n\\n9 \"display_name\": \"\"\\n\\n\\n\\n10 }\\'\\n```\\n\\nShow more\\n```\\n\\n**Expected successful response:**\\n\\n```\\n```\\n1 {\\n\\n\\n\\n2 \"auth_connection\": {\\n\\n\\n\\n3 \"id\": \"con_12345678\",\\n\\n\\n\\n4 \"display_name\": \"\",\\n\\n\\n\\n5 \"enabled\":", + "id": "ART-1966_KNOWLEDGE_NODE-25", + "text": "connection](#step-2-enable-the-authentication-connection)\\n* [Step 3: Test and verify the setup](#step-3-test-and-verify-the-setup)\\n* [Step 4: Manage authentication methods (Optional)](#step-4-manage-authentication-methods-optional)\\n* [IDP initiated SSO (Optional)](#idp-initiated-sso-optional)\\n* [Parameter reference](#parameter-reference)\\n* [Troubleshooting](#troubleshooting)\\n\\n1. [Documentation](/docs)\\n3. [Computer by DevRev](/docs/intro)\\n[External identity provider", "title": "External identity provider setup | Computer by DevRev | DevRev" }, { - "id": "ART-1966_KNOWLEDGE_NODE-30", - "text": "urn:auth0:tf-devrev-prod:\\n * **Reply URL** (Assertion Consumer Service URL): https://auth.devrev.ai/login/callback?connection=\\n * **Sign on URL**: https://app.devrev.ai/\\n\\n ![]()\\n\\n The must be the same in both parameters and follow the naming pattern described earlier.\\n6. Go to **Copy > SAML Certificates** and save the **App Federation Metadata URL**.\\n7. In the Azure portal, go to the application named", + "id": "ART-1966_KNOWLEDGE_NODE-42", + "text": "process from your identity provider\\'s portal. The latter is not supported on DevRev.\\n\\nA workaround for supporting IDP-initiated SSO is to bookmark your DevRev workspace URL (that is https://app.devrev.ai/) in your IDP. With only SSO Auth connection enabled, the experience would be as seamless as SP-initiated SSO.\\n\\n### Parameter reference\\n\\n* : Your Personal Access Token with admin permissions\\n* : Your DevRev organization ID (from the initial API", "title": "External identity provider setup | Computer by DevRev | DevRev" }, { - "id": "ART-4275_KNOWLEDGE_NODE-27", - "text": "Documentation](https://support.google.com/cloudidentity/answer/10070793).\\n* Enable contact sharing in directory settings, following guidelines provided by Google.\\n* Ensure the following scopes are added:\\n\\n + https://www.googleapis.com/auth/cloud-identity.groups.readonly: Required\\n for groups and group members.\\n + https://www.googleapis.com/auth/directory.readonly: Required for the People\\n API.\\n\\nThese steps are necessary only if a non-admin initiates the import before an\\nadmin", - "title": "Google Docs | AirSync | Snap-ins | DevRev" + "id": "ART-12476_KNOWLEDGE_NODE-1", + "text": "designed to meet GDPR and SOC 2 compliance requirements, with controls in place to support your data privacy needs.\\n\\nAdvanced enterprise login: Seamless SAML compliance for all enterprise logins regardless of your SSO provider.\\n\\nRegional data residency options: We offer data residency options in Europe, Australia, US East (Virginia), and India, with logical data isolation and access control features.\\n\\nSelf-serve user management: Easily add or remove users from your workspace and manage", + "title": "The Future of Sessions - Powered By DevRev" }, { - "id": "ART-15369_KNOWLEDGE_NODE-3", - "text": "encapsulating the configuration parameters for a Google Apps\\nauthentication connection.\\n\\nShow 5 properties\\n\\nOR\\n\\noidcobjectRequired\\n\\nObject encapsulating the configuration parameters for an OIDC\\nauthentication connection.\\n\\nShow 5 properties\\n\\nOR\\n\\noktaobjectRequired\\n\\nObject encapsulating the configuration parameters for an Okta\\nauthentication connection.\\n\\nShow 5 properties\\n\\nOR\\n\\nsamlpobjectRequired\\n\\nObject encapsulating the configuration parameters for a", - "title": "Create Dev Orgs Auth Connection | DevRev | Docs" + "id": "ART-4052_KNOWLEDGE_NODE-1", + "text": "authentication connections, refer to [External identity provider setup](https://docs.devrev.ai/product/sso-saml).\\n\\nWas this page helpful?YesNo\\n\\n[Security tokensUp Next](/public/api-reference/auth-tokens/security-tokens)\\n\\n[Built with](https://buildwithfern.com/?utm_campaign=buildWith&utm_medium=docs&utm_source=developer.devrev.ai)\\n\\n[Enterprise grade security to protect customer dataLearn more about it.](https://devrev.ai/blog/soc-compliance)\\n\\nProduct\\n\\n *", + "title": "Identity provider \u2014 DevRev | Docs" }, { - "id": "ART-1966_KNOWLEDGE_NODE-40", - "text": "\\'Authorization: Bearer \\'\\n```\\n```\\n\\nLook for the Google OAuth connection in the response and note its id field.\\n\\nDisable Google authentication:\\n\\n```\\n```\\n1 curl --location --request POST \\'https://api.devrev.ai/dev-orgs.auth-connections.toggle\\' \\\\\\n\\n\\n\\n2 --header \\'Authorization: Bearer \\' \\\\\\n\\n\\n\\n3 --header \\'Content-Type: application/json\\' \\\\\\n\\n\\n\\n4 --data-raw \\'{\\n\\n\\n\\n5 \"id\": \"\",\\n\\n\\n\\n6 \"toggle\": \"disable\"\\n\\n\\n\\n7", - "title": "External identity provider setup | Computer by DevRev | DevRev" + "id": "ART-15701_KNOWLEDGE_NODE-25", + "text": "session expired, contact your administrator to check with the SAML login setup with AWS and IdP.\\n\\nCheck if [https://app.devrev.ai](https://app.devrev.ai) is added approved domain in Approved Origins tab. Check Point 2 of Setup DevRev Integration with Amazon Connect for more information on this.\\n\\nConfirm your credentials with the administrator and try again.\\n\\nQ: How to port existing phone number to Amazon Connect?\\n\\nIf you already have a phone number and want to port it to Amazon Connect", + "title": "Amazon Connect Telephony Integration Guide" } ] }, @@ -284,19 +284,14 @@ "query": "restrict users from linking opportunities and meetings", "retrievals": [ { - "id": "ART-15404_KNOWLEDGE_NODE-7", - "text": "Error\\n\\n401\\n\\nUnauthorized Error\\n\\n403\\n\\nForbidden Error\\n\\n429\\n\\nToo Many Requests Error\\n\\n500\\n\\nInternal Server Error\\n\\n503\\n\\nService Unavailable Error\\n\\nWas this page helpful?\\n\\nYesNo\\n\\n[Previous](/api-reference/links/list-post)[#### Count Meetings\\n\\nNext](/api-reference/meetings/count)[Built with](https://buildwithfern.com/?utm_campaign=buildWith&utm_medium=docs&utm_source=developer.devrev.ai)'", - "title": "Replace Links | DevRev | Docs" - }, - { - "id": "ART-13009_KNOWLEDGE_NODE-3", - "text": "meeting.\\n\\nlinks.targetstringOptional`format: \"id\"`\\n\\nFilters for target id in links associated with the meeting.\\n\\nlinks.target_object_typestringOptional`format: \"text\"`\\n\\nFilters for target object type in links associated with the meeting.\\n\\nmemberslist of stringsOptional\\n\\nFilter for meeting on specified Member Ids.\\n\\nmodeenumOptional\\n\\nThe iteration mode to use, otherwise if not set, then \\xe2\\x80\\x9cafter\\xe2\\x80\\x9d is used.\\n\\nAllowed values: afterbefore\\n\\norganizerlist of", - "title": "List Meetings \u2014 DevRev | Docs" + "id": "ART-13005_KNOWLEDGE_NODE-2", + "text": "stringsOptional\\n\\nFilters for meetings created by the specified user(s).\\n\\nexternal_reflist of stringsOptional\\n\\nFilters for meetings with the provided external_ref(s).\\n\\nlinks.link_typestringOptional`format: \"text\"`\\n\\nFilters for link type in links associated with the meeting.\\n\\nlinks.targetstringOptional`format: \"id\"`\\n\\nFilters for target id in links associated with the meeting.\\n\\nlinks.target_object_typestringOptional`format: \"text\"`\\n\\nFilters for target object type in links", + "title": "Count Meetings \u2014 DevRev | Docs" }, { - "id": "ART-3008_KNOWLEDGE_NODE-2", - "text": "meeting.\\n\\nlinks.targetstringOptional`format: \"id\"`\\n\\nFilters for target id in links associated with the meeting.\\n\\nlinks.target_object_typestringOptional`format: \"text\"`\\n\\nFilters for target object type in links associated with the meeting.\\n\\nmemberslist of stringsOptional\\n\\nFilter for meeting on specified Member Ids.\\n\\nmodeenumOptional\\n\\nThe iteration mode to use, otherwise if not set, then \\xe2\\x80\\x9cafter\\xe2\\x80\\x9d is used.\\n\\nAllowed values: afterbefore\\n\\norganizerlist of", - "title": "List Meetings (Beta) \u2014 DevRev | Docs" + "id": "ART-3003_KNOWLEDGE_NODE-1", + "text": "user(s).\\n\\ncustom_fieldsobjectOptional\\n\\nFilters for meeting on custom fields.\\n\\nexternal_reflist of stringsOptional\\n\\nFilters for meetings with the provided external_ref(s).\\n\\nlinks.link_typestringOptional`format: \"text\"`\\n\\nFilters for link type in links associated with the meeting.\\n\\nlinks.targetstringOptional`format: \"id\"`\\n\\nFilters for target id in links associated with the meeting.\\n\\nlinks.target_object_typestringOptional`format: \"text\"`\\n\\nFilters for target object type in links", + "title": "Count Meetings (Beta) \u2014 DevRev | Docs" }, { "id": "ART-13009_KNOWLEDGE_NODE-2", @@ -304,14 +299,9 @@ "title": "List Meetings \u2014 DevRev | Docs" }, { - "id": "ART-15422_KNOWLEDGE_NODE-5", - "text": "return.\\n\\nlinks.link\\\\_typestringOptional`format: \"text\"`\\n\\nFilters for link type in links associated with the meeting.\\n\\nlinks.targetstringOptional`format: \"id\"`\\n\\nFilters for target id in links associated with the meeting.\\n\\nlinks.target\\\\_object\\\\_typestringOptional`format: \"text\"`\\n\\nFilters for target object type in links associated with the meeting.\\n\\nmemberslist of stringsOptional\\n\\nFilter for meeting on specified Member Ids.\\n\\nmodeenumOptional\\n\\nThe iteration mode to use,", - "title": "List Meetings | DevRev | Docs" - }, - { - "id": "ART-1834_KNOWLEDGE_NODE-456", - "text": "set, then \"after\" is used.\\nAllowed values: after before\\nopportunity.account string Optional\\nFilters for opportunities belonging to any of the provided accounts.\\nopportunity.contacts string Optional\\nFilters for opportunities with any of the provided contacts.\\nopportunity.subtype string Optional\\nFilters for opportunity with any of the provided subtypes.\\nowned_by string Optional\\nFilters for work owned by any of these users.\\nreported_by string Optional\\nFilters for work reported by any of", - "title": "Delete \u2014 DevRev | Docs" + "id": "ART-15416_KNOWLEDGE_NODE-2", + "text": "created by the specified user(s).\\n\\nexternal\\\\_reflist of stringsOptional\\n\\nFilters for meetings with the provided external\\\\_ref(s).\\n\\nlinks.link\\\\_typestringOptional`format: \"text\"`\\n\\nFilters for link type in links associated with the meeting.\\n\\nlinks.targetstringOptional`format: \"id\"`\\n\\nFilters for target id in links associated with the meeting.\\n\\nlinks.target\\\\_object\\\\_typestringOptional`format: \"text\"`\\n\\nFilters for target object type in links associated with the", + "title": "Count Meetings | DevRev | Docs" }, { "id": "ART-3008_KNOWLEDGE_NODE-1", @@ -319,19 +309,29 @@ "title": "List Meetings (Beta) \u2014 DevRev | Docs" }, { - "id": "ART-1575_KNOWLEDGE_NODE-449", - "text": "opportunities with any of the provided contacts.\\nopportunity.subtype string Optional\\nFilters for opportunity with any of the provided subtypes.\\nowned_by string Optional\\nFilters for work owned by any of these users.\\nreported_by string Optional\\nFilters for work reported by any of these users.\\nsort_by string Optional\\nFields to sort the work items by and the direction to sort them.\\nstage.name string Optional\\nFilters for records in the provided stage(s) by name.\\nstaged_info.is_staged", - "title": "Delete \u2014 DevRev | Docs" + "id": "ART-15422_KNOWLEDGE_NODE-5", + "text": "return.\\n\\nlinks.link\\\\_typestringOptional`format: \"text\"`\\n\\nFilters for link type in links associated with the meeting.\\n\\nlinks.targetstringOptional`format: \"id\"`\\n\\nFilters for target id in links associated with the meeting.\\n\\nlinks.target\\\\_object\\\\_typestringOptional`format: \"text\"`\\n\\nFilters for target object type in links associated with the meeting.\\n\\nmemberslist of stringsOptional\\n\\nFilter for meeting on specified Member Ids.\\n\\nmodeenumOptional\\n\\nThe iteration mode to use,", + "title": "List Meetings | DevRev | Docs" }, { - "id": "ART-1821_KNOWLEDGE_NODE-446", - "text": "opportunities with any of the provided contacts.\\nopportunity.subtype string Optional\\nFilters for opportunity with any of the provided subtypes.\\nowned_by string Optional\\nFilters for work owned by any of these users.\\nreported_by string Optional\\nFilters for work reported by any of these users.\\nsort_by string Optional\\nFields to sort the work items by and the direction to sort them.\\nstage.name string Optional\\nFilters for records in the provided stage(s) by name.\\nstaged_info.is_staged", - "title": "Delete \u2014 DevRev | Docs" + "id": "ART-3002_KNOWLEDGE_NODE-1", + "text": "https://api.devrev.ai/meetings.delete \\\\ \\n ---|--- \\n >| -H \"Authorization: Bearer \" \\\\ \\n >| -H \"Content-Type: application/json\" \\\\ \\n >| -d \\'{ \\n >| \"id\": \"id\" \\n >| }\\'\\n[/code] \\n \\nTry it\\n\\n200Successful\\n\\n[code]\\n\\n 1| {} \\n ---|---\\n[/code] \\n \\n[Get MeetingUp Next](/beta/api-reference/meetings/get)\\n\\n[Built with](https://buildwithfern.com/?utm_campaign=buildWith&utm_medium=docs&utm_source=developer.devrev.ai)\\n\\n'", + "title": "Delete Meeting (Beta) \u2014 DevRev | Docs" }, { - "id": "ART-15416_KNOWLEDGE_NODE-2", - "text": "created by the specified user(s).\\n\\nexternal\\\\_reflist of stringsOptional\\n\\nFilters for meetings with the provided external\\\\_ref(s).\\n\\nlinks.link\\\\_typestringOptional`format: \"text\"`\\n\\nFilters for link type in links associated with the meeting.\\n\\nlinks.targetstringOptional`format: \"id\"`\\n\\nFilters for target id in links associated with the meeting.\\n\\nlinks.target\\\\_object\\\\_typestringOptional`format: \"text\"`\\n\\nFilters for target object type in links associated with the", - "title": "Count Meetings | DevRev | Docs" + "id": "ART-3004_KNOWLEDGE_NODE-1", + "text": "curl -X POST https://api.devrev.ai/meetings.get \\\\ \\n ---|--- \\n >| -H \"Authorization: Bearer \" \\\\ \\n >| -H \"Content-Type: application/json\" \\\\ \\n >| -d \\'{ \\n >| \"id\": \"id\" \\n >| }\\'\\n[/code] \\n \\nTry it\\n\\n200Successful\\n\\n[code]\\n\\n 1| { \\n ---|--- \\n 2| \"meeting\": { \\n 3| \"id\": \"id\", \\n 4| \"members\": [ \\n 5| { \\n 6| \"type\": \"dev_user\", \\n 7| \"id\": \"id\", \\n 8|", + "title": "Get Meeting (POST) (Beta) \u2014 DevRev | Docs" + }, + { + "id": "ART-16803_KNOWLEDGE_NODE-26", + "text": "Tickets\\n* Meetings\\n* Objects linked to issues\\n* Users\\n\\nTo configure a workspace object loop:\\n\\n1. On the **workflow canvas**, add an action step named **Loop for [Object]**, where [Object] is the entity you want to iterate over.\\n2. Apply **filter conditions** to refine the set of objects included in the loop and perform operations on them.\\n\\nAll **actions** inside the loop execute once per object that satisfies the filter conditions.\\n\\n### For Each\\n\\nThe **For Each** loop iterates", + "title": "Workflow nodes | Workflows | Computer by DevRev | DevRev" + }, + { + "id": "ART-3008_KNOWLEDGE_NODE-5", + "text": "\"Authorization: Bearer \"\\n[/code] \\n \\nTry it\\n\\n200Retrieved\\n\\n[code]\\n\\n 1| { \\n ---|--- \\n 2| \"meetings\": [ \\n 3| { \\n 4| \"id\": \"id\", \\n 5| \"members\": [ \\n 6| { \\n 7| \"type\": \"dev_user\", \\n 8| \"id\": \"id\", \\n 9| \"display_id\": \"display_id\", \\n 10| \"display_name\": \"display_name\", \\n 11| \"display_picture\": { \\n 12| \"id\": \"id\", \\n 13|", + "title": "List Meetings (Beta) \u2014 DevRev | Docs" } ] }, @@ -345,13 +345,8 @@ "title": "WhatsApp | Integrate | Snap-ins | DevRev" }, { - "id": "ART-2029_KNOWLEDGE_NODE-30", - "text": "phone number to sync WhatsApp messages sent to the business with DevRev Inbox.\\n4. **Register for WhatsApp webhook:** In the **Discussion** tab, enter **/whatsapp** to register to the WhatsApp webhook URL to receive WhatsApp messages in the DevRev Inbox.\\n5. **Use template messages:** As per WhatsApp policies, template messages are required to communicate with customers once 24 hours have passed since their last message. To ensure continuity in customer conversations, the following template", - "title": "WhatsApp | Integrate | Snap-ins | DevRev" - }, - { - "id": "ART-2029_KNOWLEDGE_NODE-27", - "text": "work with 360dialog for WhatsApp Integration. If you have an existing WhatsApp for Business Account, follow the steps to [migrate to 360dialog](https://docs.360dialog.com/partner/account-setup/migrating-phone-numbers).\\n\\nInstalling the WhatsApp snap-in\\n-------------------------------\\n\\nTo use this snap-in, you\\'ll need to connect your WhatsApp with Business API with DevRev.\\n\\n1. Install [WhatsApp](/marketplace/whatsapp) from the DevRev marketplace.\\n2. Select the workspace to install the", + "id": "ART-2029_KNOWLEDGE_NODE-28", + "text": "snap-in, confirm installation, and click **Deploy snap-in**.\\n\\nLimitations\\n-----------\\n\\n* Group Conversations are not supported by WhatsApp for Business API.\\n* If you do not respond to the customer\\xe2\\x80\\x99s message within 24 hours, you can only respond to the conversation using Meta-approved template messages.\\n\\nSet up the snap-in\\n------------------\\n\\nFollow these steps to ensure WhatsApp messages sent to your business are synced with the DevRev Inbox.\\n\\n1. **Install the snap-in:**", "title": "WhatsApp | Integrate | Snap-ins | DevRev" }, { @@ -360,34 +355,39 @@ "title": "WhatsApp | Integrate | Snap-ins | DevRev" }, { - "id": "ART-2029_KNOWLEDGE_NODE-28", - "text": "snap-in, confirm installation, and click **Deploy snap-in**.\\n\\nLimitations\\n-----------\\n\\n* Group Conversations are not supported by WhatsApp for Business API.\\n* If you do not respond to the customer\\xe2\\x80\\x99s message within 24 hours, you can only respond to the conversation using Meta-approved template messages.\\n\\nSet up the snap-in\\n------------------\\n\\nFollow these steps to ensure WhatsApp messages sent to your business are synced with the DevRev Inbox.\\n\\n1. **Install the snap-in:**", + "id": "ART-2029_KNOWLEDGE_NODE-30", + "text": "phone number to sync WhatsApp messages sent to the business with DevRev Inbox.\\n4. **Register for WhatsApp webhook:** In the **Discussion** tab, enter **/whatsapp** to register to the WhatsApp webhook URL to receive WhatsApp messages in the DevRev Inbox.\\n5. **Use template messages:** As per WhatsApp policies, template messages are required to communicate with customers once 24 hours have passed since their last message. To ensure continuity in customer conversations, the following template", "title": "WhatsApp | Integrate | Snap-ins | DevRev" }, { "id": "ART-2029_KNOWLEDGE_NODE-29", - "text": "Install the WhatsApp snap-in from the marketplace as mentioned above.\\n2. **Create a connection:** In the **Connections** tab, add your existing connection or create a new connection.\\n * Give your connection a name, and ensure that you completed the required steps in the prerequisites.\\n * Click **Connect**.\\n * Open the dialog and follow the process to finish creating a connection.\\n\\n ![]()\\n3. **Configure business phone number:** In the **Configuration** tab, enter the business", + "text": "Install the WhatsApp snap-in from the marketplace as mentioned above.\\n2. **Create a connection:** In the **Connections** tab, add your existing connection or create a new connection.\\n * Give your connection a name, and ensure that you completed the required steps in the prerequisites.\\n * Click **Connect**.\\n * Open the dialog and follow the process to finish creating a connection.\\n\\n ![]()\\n3. **Configure business phone number:** In the **Configuration** tab, enter the business", "title": "WhatsApp | Integrate | Snap-ins | DevRev" }, { - "id": "ART-2029_KNOWLEDGE_NODE-26", - "text": "Business Manager. For detailed information, refer to [creating a Business Account](https://m.facebook.com/help/1710077379203657) in Meta Business Manager.\\n2. **Number compatibility:** Ensure the designated number isn\\'t linked to another WhatsApp account. If it is, either delete that account or [migrate your number](https://developers.facebook.com/docs/whatsapp/cloud-api/get-started/migrate-existing-whatsapp-number-to-a-business-account/) to a business account.\\n3. **Partner integration:** We", - "title": "WhatsApp | Integrate | Snap-ins | DevRev" + "id": "ART-2002_KNOWLEDGE_NODE-35", + "text": "integrations like [Slack](/marketplace/slack), [Email for conversations](https://marketplace.devrev.ai/marketplace/devrev-plug-with-email), [WhatsApp](/marketplace/whatsapp) are additional channels available with DevRev's omnichannel support offering.\\nIntegrating these channels automatically brings customer identity to DevRev.\\n\\n[PreviousOpportunities](/docs/product/opportunity)[NextAccount and contact import](/docs/product/account-contact-import)\\n\\n#### On this page\\n\\n*", + "title": "Contacts | Computer for Growth Teams | DevRev" }, { - "id": "ART-2029_KNOWLEDGE_NODE-23", - "text": "2025](/docs/changelog/_2025-06-01)\\n + [May 2025](/docs/changelog/_2025-05-01)\\n + [March and April 2025](/docs/changelog/_2025-04-01)\\n + [February 2025](/docs/changelog/_2025-02-01)\\n* [Developer \\xe2\\x86\\x97\\xef\\xb8\\x8f](https://developer.devrev.ai/)\\n* [DevRevU \\xe2\\x86\\x97\\xef\\xb8\\x8f](/docs/DevRevU)\\n\\n + [Product demos](/docs/DevRevU/demos)\\n\\nOn this page\\n\\n* [Prerequisites](#prerequisites)\\n* [Installing the WhatsApp snap-in](#installing-the-whatsapp-snapin)\\n*", - "title": "WhatsApp | Integrate | Snap-ins | DevRev" + "id": "ART-15716_KNOWLEDGE_NODE-20", + "text": "them, reach out to DevRev support with details (article titles, migration date, etc.) for assistance.\\n\\nSupport for Incoming Text Messages (SMS and WhatsApp)\\n\\nYes, DevRev does allow for incoming text messages\\xe2\\x80\\x94if you use a supported SMS integration.\\n\\nThe main provider currently supported is Exotel. When you connect your Exotel account to DevRev, customers can send SMS to your Exotel number, and those messages will show up as conversations in your DevRev inbox.\\n\\nWhatsApp is also", + "title": "Support queries related playbook" }, { "id": "ART-2029_KNOWLEDGE_NODE-0", - "text": "b'WhatsApp | Integrate | Snap-ins | DevRev\\n\\n* Computer\\n* Resources\\n* [Our Customers](/case-study)\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](/request-a-demo)\\n\\nComputer\\n\\nResources\\n\\n[Our Customers](/case-study)\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](/request-a-demo)\\n\\nSearch\\n\\n`CTRL`\\xc2\\xa0+\\xc2\\xa0`K`\\n\\n* [Introduction](/docs)\\n* [Computer by DevRev](/docs/intro)\\n\\n + [Core concepts](/docs/product/core)\\n + [Apps](/docs/product/apps)\\n +", + "text": "b'WhatsApp | Integrate | Snap-ins | DevRev\\n\\n* Computer\\n* Resources\\n* [Our Customers](/case-study)\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](/request-a-demo)\\n\\nComputer\\n\\nResources\\n\\n[Our Customers](/case-study)\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](/request-a-demo)\\n\\nSearch\\n\\n`CTRL`\\xc2\\xa0+\\xc2\\xa0`K`\\n\\n* [Introduction](/docs)\\n* [Computer by DevRev](/docs/intro)\\n\\n + [Core concepts](/docs/product/core)\\n + [Apps](/docs/product/apps)\\n +", "title": "WhatsApp | Integrate | Snap-ins | DevRev" }, { "id": "ART-2002_KNOWLEDGE_NODE-27", "text": "Plug, email, and WhatsApp) can be matched to the right customer record.\\n\\n![]()\\n\\nYou can create a contact using DevRev's rev-users.create API. Follow the [Create accounts and contacts in DevRev](https://developer.devrev.ai/beta/guides/create-accounts-and-contacts-in-dev-rev) tutorial.\\n\\n### Bulk import customer records\\n\\nTo bulk import customer records, see [Account and contact import](/docs/product/account-contact-import).\\n\\nYou can also use [AirSync](https://docs.devrev.ai/import) to", "title": "Contacts | Computer for Growth Teams | DevRev" + }, + { + "id": "ART-2035_KNOWLEDGE_NODE-61", + "text": "them.\\n* As of the latest update, in case of unavailability of email, the snap-in creates new DevRev contact and attaches Slack user id for future reference. For legacy users, run the /AddSlackUserId command in DevRev on the Contacts to manually add their Slack user ID.\\n\\n[PreviousExotel](/docs/integrations/exotel)[NextWhatsApp](/docs/integrations/whatsapp)\\n\\n#### On this page\\n\\n* [Installation](#installation)\\n* [List of available commands](#list-of-available-commands)\\n* [Create DevRev", + "title": "Slack | Integrate | Snap-ins | DevRev" } ] }, @@ -395,55 +395,55 @@ "query_id": "9a4adb6b-b6f7-430a-a599-07aea5d4c365", "query": "API for Incident Ticket creation", "retrievals": [ - { - "id": "ART-4127_KNOWLEDGE_NODE-0", - "text": "b'Create Incident | DevRev | Docs\\n\\n[![]()![]()](https://developer.devrev.ai/)\\n\\nBeta\\n\\nBeta\\n\\nBeta\\n\\nSearch\\n\\n`/`\\n\\n[API Reference](/beta/api-reference/accounts/create)[incidents](/beta/api-reference/incidents/create)\\n\\nCreate Incident\\n===============\\n\\nBeta\\n\\nCopy page\\n\\nPOST\\n\\nhttps://api.devrev.ai/incidents.create\\n\\nPOST\\n\\n/incidents.create\\n\\ncURL\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl -X POST https://api.devrev.ai/incidents.create \\\\ |\\n| > | -H \"Authorization: Bearer", - "title": "Create Incident | DevRev | Docs" - }, { "id": "ART-4127_KNOWLEDGE_NODE-1", - "text": "\" \\\\ |\\n| > | -H \"Content-Type: application/json\" \\\\ |\\n| > | -d \\'{ |\\n| > | \"title\": \"string\" |\\n| > | }\\' |\\n```\\n\\n[Try it](/beta/api-reference/incidents/create?explorer=true)\\n\\n201Created\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | { |\\n| 2 | \"incident\": { |\\n| 3 | \"id\": \"string\", |\\n| 4 | \"title\": \"string\", |\\n| 5 | \"acknowledged_date\": \"2023-01-01T12:00:00.000Z\", |\\n| 6 | \"actual_close_date\": \"2023-01-01T12:00:00.000Z\", |\\n| 7 | \"applies_to_parts\": [ |\\n| 8 | { |\\n| 9 | \"display_id\":", + "text": "\" \\\\ |\\n| > | -H \"Content-Type: application/json\" \\\\ |\\n| > | -d \\'{ |\\n| > | \"title\": \"string\" |\\n| > | }\\' |\\n```\\n\\n[Try it](/beta/api-reference/incidents/create?explorer=true)\\n\\n201Created\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | { |\\n| 2 | \"incident\": { |\\n| 3 | \"id\": \"string\", |\\n| 4 | \"title\": \"string\", |\\n| 5 | \"acknowledged_date\": \"2023-01-01T12:00:00.000Z\", |\\n| 6 | \"actual_close_date\": \"2023-01-01T12:00:00.000Z\", |\\n| 7 | \"applies_to_parts\": [ |\\n| 8 | { |\\n| 9 | \"display_id\":", "title": "Create Incident | DevRev | Docs" }, { - "id": "ART-12390_KNOWLEDGE_NODE-29", - "text": "Ticket | Creates a new ticket in DevRev. | * Ticket details like title, body, applies\\\\_to\\\\_part, etc. * subtype: (Optional) Ticket subtype * apps: (Optional) Related apps * app\\\\_custom\\\\_fields: (Optional) Custom fields | Created ticket object |\\n| Convert Conversation To Ticket | Converts a conversation to a ticket. | * conversation\\\\_id: ID of the conversation to convert | ticket\\\\_id: ID of the created ticket |\\n\\nObject retrieval\\n----------------\\n\\n| Operation | Description | Input", - "title": "Workflow action library | Workflows | Computer by DevRev | DevRev" + "id": "ART-1564_KNOWLEDGE_NODE-244", + "text": "owner.\\n\\nResponse.\\n\\nThis endpoint returns an object.\\ngroup object\\nShow 11 properties\\nAPI Reference operate Incidents Create.\\n\\nPOST https://api.devrev.ai / incidents.create\\n\\nCreates an incident.\\n\\nRequest.\\n\\nThis endpoint expects an object.\\ntitle string Required\\n\\nTitle of the incident.\\n\\nacknowledged_date datetime Optional\\n\\nTimestamp when the incident was acknowledged.\\n\\napplies_to_parts list of strings Optional\\n\\nParts to which the incident is applicable to.\\n\\nartifacts", + "title": "List (Beta) \u2014 DevRev | Docs" }, { - "id": "ART-4126_KNOWLEDGE_NODE-0", - "text": "b'Get Incident (POST) | DevRev | Docs\\n\\n[![]()![]()](https://developer.devrev.ai/)\\n\\nBeta\\n\\nBeta\\n\\nBeta\\n\\nSearch\\n\\n`/`\\n\\n[API Reference](/beta/api-reference/accounts/create)[incidents](/beta/api-reference/incidents/create)\\n\\nGet Incident (POST)\\n===================\\n\\nBeta\\n\\nCopy page\\n\\nPOST\\n\\nhttps://api.devrev.ai/incidents.get\\n\\nPOST\\n\\n/incidents.get\\n\\ncURL\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl -X POST https://api.devrev.ai/incidents.get \\\\ |\\n| > | -H \"Authorization: Bearer", - "title": "Get Incident (POST) | DevRev | Docs" + "id": "ART-1791_KNOWLEDGE_NODE-165", + "text": "Create.\\n\\nPOST https:// api.devrev.ai / incidents.create\\nCreates an incident.\\nRequest.\\n\\nThis endpoint expects an object.\\ntitle string Required\\nTitle of the incident.\\nacknowledged_date datetime Optional\\nTimestamp when the incident was acknowledged.\\napplies_to_parts list of strings Optional\\nParts to which the incident is applicable to.\\nartifacts list of strings Optional\\nArtifacts attached to the incident.\\nbody string Optional\\nBody of the incident.\\ncustom_fields map from strings to", + "title": "Self Delete \u2014 DevRev | Docs" }, { - "id": "ART-4127_KNOWLEDGE_NODE-15", - "text": "\"string\" |\\n| 258 | } |\\n| 259 | ], |\\n| 260 | \"target_close_date\": \"2023-01-01T12:00:00.000Z\" |\\n| 261 | } |\\n| 262 | } |\\n```\\n\\nCreates an incident.\\n\\n### Headers\\n\\nAuthorizationstringRequired\\n\\nBearer authentication of the form `Bearer `, where token is your auth token.\\n\\n### Request\\n\\nThis endpoint expects an object.\\n\\ntitlestringRequired`format: \"text\"`\\n\\nTitle of the incident.\\n\\nacknowledged\\\\_datestringOptional`format: \"date-time\"`\\n\\nTimestamp when the incident was", - "title": "Create Incident | DevRev | Docs" + "id": "ART-1781_KNOWLEDGE_NODE-164", + "text": "Create.\\n\\nPOST https:// api.devrev.ai / incidents.create\\nCreates an incident.\\nRequest.\\n\\nThis endpoint expects an object.\\ntitle string Required\\nTitle of the incident.\\nacknowledged_date datetime Optional\\nTimestamp when the incident was acknowledged.\\napplies_to_parts list of strings Optional\\nParts to which the incident is applicable to.\\nartifacts list of strings Optional\\nArtifacts attached to the incident.\\nbody string Optional\\nBody of the incident.\\ncustom_fields map from strings to", + "title": "List \u2014 DevRev | Docs" }, { - "id": "ART-4133_KNOWLEDGE_NODE-0", - "text": "b'Update Incident | DevRev | Docs\\n\\n[![]()![]()](https://developer.devrev.ai/)\\n\\nBeta\\n\\nBeta\\n\\nBeta\\n\\nSearch\\n\\n`/`\\n\\n[API Reference](/beta/api-reference/accounts/create)[incidents](/beta/api-reference/incidents/create)\\n\\nUpdate Incident\\n===============\\n\\nBeta\\n\\nCopy page\\n\\nPOST\\n\\nhttps://api.devrev.ai/incidents.update\\n\\nPOST\\n\\n/incidents.update\\n\\ncURL\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl -X POST https://api.devrev.ai/incidents.update \\\\ |\\n| > | -H \"Authorization: Bearer", - "title": "Update Incident | DevRev | Docs" + "id": "ART-1803_KNOWLEDGE_NODE-167", + "text": "Create.\\n\\nPOST https:// api.devrev.ai / incidents.create\\nCreates an incident.\\nRequest.\\n\\nThis endpoint expects an object.\\ntitle string Required\\nTitle of the incident.\\nacknowledged_date datetime Optional\\nTimestamp when the incident was acknowledged.\\napplies_to_parts list of strings Optional\\nParts to which the incident is applicable to.\\nartifacts list of strings Optional\\nArtifacts attached to the incident.\\nbody string Optional\\nBody of the incident.\\ncustom_fields map from strings to", + "title": "List \u2014 DevRev | Docs" }, { - "id": "ART-2033_KNOWLEDGE_NODE-5", - "text": "ticket conversion](/docs/product/conversation-ticket)\\n + [Tickets](/docs/product/tickets)\\n + [Routing](/docs/product/routing)\\n + [Support best practices](/docs/product/support-bp)\\n + [Customer portal](/docs/product/support-portal)\\n + [Questions & answers](/docs/product/qa)\\n + [Knowledge Base](/docs/product/knowledge-base)\\n\\n - [Articles](/docs/product/articles)\\n - [Collections](/docs/product/collection)\\n + [Turing AI agent](/docs/product/conversational-bot)\\n\\n - [Best", - "title": "Instabug | Integrate | Snap-ins | DevRev" + "id": "ART-1788_KNOWLEDGE_NODE-166", + "text": "Create.\\n\\nPOST https:// api.devrev.ai / incidents.create\\nCreates an incident.\\nRequest.\\n\\nThis endpoint expects an object.\\ntitle string Required\\nTitle of the incident.\\nacknowledged_date datetime Optional\\nTimestamp when the incident was acknowledged.\\napplies_to_parts list of strings Optional\\nParts to which the incident is applicable to.\\nartifacts list of strings Optional\\nArtifacts attached to the incident.\\nbody string Optional\\nBody of the incident.\\ncustom_fields map from strings to", + "title": "Get Post \u2014 DevRev | Docs" }, { - "id": "ART-1801_KNOWLEDGE_NODE-168", + "id": "ART-1805_KNOWLEDGE_NODE-167", "text": "Create.\\n\\nPOST https:// api.devrev.ai / incidents.create\\nCreates an incident.\\nRequest.\\n\\nThis endpoint expects an object.\\ntitle string Required\\nTitle of the incident.\\nacknowledged_date datetime Optional\\nTimestamp when the incident was acknowledged.\\napplies_to_parts list of strings Optional\\nParts to which the incident is applicable to.\\nartifacts list of strings Optional\\nArtifacts attached to the incident.\\nbody string Optional\\nBody of the incident.\\ncustom_fields map from strings to", - "title": "Get \u2014 DevRev | Docs" + "title": "List Post \u2014 DevRev | Docs" }, { - "id": "ART-4128_KNOWLEDGE_NODE-0", - "text": "b'Get Incident | DevRev | Docs\\n\\n[![]()![]()](https://developer.devrev.ai/)\\n\\nBeta\\n\\nBeta\\n\\nBeta\\n\\nSearch\\n\\n`/`\\n\\n[API Reference](/beta/api-reference/accounts/create)[incidents](/beta/api-reference/incidents/create)\\n\\nGet Incident\\n============\\n\\nBeta\\n\\nCopy page\\n\\nGET\\n\\nhttps://api.devrev.ai/incidents.get\\n\\nGET\\n\\n/incidents.get\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl -G https://api.devrev.ai/incidents.get \\\\ |\\n| > | -H \"Authorization: Bearer \" \\\\ |\\n| > | -d id=id", - "title": "Get Incident | DevRev | Docs" + "id": "ART-1307_KNOWLEDGE_NODE-167", + "text": "Create.\\n\\nPOST https:// api.devrev.ai / incidents.create\\nCreates an incident.\\nRequest.\\n\\nThis endpoint expects an object.\\ntitle string Required\\nTitle of the incident.\\nacknowledged_date datetime Optional\\nTimestamp when the incident was acknowledged.\\napplies_to_parts list of strings Optional\\nParts to which the incident is applicable to.\\nartifacts list of strings Optional\\nArtifacts attached to the incident.\\nbody string Optional\\nBody of the incident.\\ncustom_fields map from strings to", + "title": "List Post \u2014 DevRev | Docs" }, { - "id": "ART-1803_KNOWLEDGE_NODE-167", + "id": "ART-1789_KNOWLEDGE_NODE-166", "text": "Create.\\n\\nPOST https:// api.devrev.ai / incidents.create\\nCreates an incident.\\nRequest.\\n\\nThis endpoint expects an object.\\ntitle string Required\\nTitle of the incident.\\nacknowledged_date datetime Optional\\nTimestamp when the incident was acknowledged.\\napplies_to_parts list of strings Optional\\nParts to which the incident is applicable to.\\nartifacts list of strings Optional\\nArtifacts attached to the incident.\\nbody string Optional\\nBody of the incident.\\ncustom_fields map from strings to", "title": "List \u2014 DevRev | Docs" + }, + { + "id": "ART-1300_KNOWLEDGE_NODE-166", + "text": "Create.\\n\\nPOST https:// api.devrev.ai / incidents.create\\nCreates an incident.\\nRequest.\\n\\nThis endpoint expects an object.\\ntitle string Required\\nTitle of the incident.\\nacknowledged_date datetime Optional\\nTimestamp when the incident was acknowledged.\\napplies_to_parts list of strings Optional\\nParts to which the incident is applicable to.\\nartifacts list of strings Optional\\nArtifacts attached to the incident.\\nbody string Optional\\nBody of the incident.\\ncustom_fields map from strings to", + "title": "Create \u2014 DevRev | Docs" } ] }, @@ -452,54 +452,54 @@ "query": "mark fields as readable from backend", "retrievals": [ { - "id": "ART-17232_KNOWLEDGE_NODE-8", - "text": "fields |\\n\\n### Custom and stock fields transformation methods\\n\\n| Method | Description | Requirements |\\n| --- | --- | --- |\\n| `use_rich_text` | Produces a rich text field | External field must be of type `rich_text` |\\n\\n### Constructed custom fields transformation methods\\n\\n| Method | Description | Requirements |\\n| --- | --- | --- |\\n| `construct_text_field` | Produces a text field | External field must be of type text |\\n\\n### Universal transformation method\\n\\n| Method | Description |", - "title": "Mapping reasons | DevRev | Docs" + "id": "ART-1645_KNOWLEDGE_NODE-37", + "text": "`is_filterable` to be true.\\n\\n * `is_groupable`: Whether the field is groupable. Requires `is_filterable` to be true.\\n\\n * `order`: The order in which the field appears in the side panel.\\n\\n * `is_read_only`: Whether the field is read-only in the UI. Once the object is created, this field cannot be updated in the UI.\\n\\n * `group_name`: The group title under which field(s) appear in the side panel. In the example below, the fields are grouped under groups titled **Group 1** and **Group", + "title": "Object customization (Beta) \u2014 DevRev | Docs" }, { - "id": "ART-17230_KNOWLEDGE_NODE-0", - "text": "b'Rich text fields | DevRev | Docs\\n\\n[![]()![]()](https://developer.devrev.ai/)\\n\\nPublic\\n\\nPublic\\n\\nSearch\\n\\n`/`\\n\\nOn this page\\n\\n* [Rich text mentions](/airsync/data-model/rich-text-fields#rich-text-mentions)\\n* [Importing articles](/airsync/data-model/rich-text-fields#importing-articles)\\n* [Managing permissions](/airsync/data-model/rich-text-fields#managing-permissions)\\n* [Inline attachments](/airsync/data-model/rich-text-fields#inline-attachments)\\n* [Links to other", - "title": "Rich text fields | DevRev | Docs" + "id": "ART-996_KNOWLEDGE_NODE-15", + "text": "field1\\n ...\\n gateway:\\n api_visibility: public\\n is_filterable: true\\n summary: true # NOTE: all fields marked as `summary: true`\\n...\\n - name: field2\\n ...\\n gateway:\\n api_visibility: public\\n is_filterable: true\\n summary: true # NOTE: all fields marked as `summary: true`\\n...\\n - name: field3\\n ...\\n gateway:\\n api_visibility:", + "title": "An Example Object Model Style Guide (our actual style guide)" }, { - "id": "ART-15510_KNOWLEDGE_NODE-17", - "text": "server. Input views such as password text fields are automatically masked.\\n\\nWhile the auto-masking feature is sufficient for most situations, you can manually mark or unmark additional views as sensitive.\\n\\nTo mark elements as sensitive inside a web view (`WebView`), apply the `devrev-mask` CSS class. To unmark them, use `devrev-unmask`.\\n\\n* Mark an element as masked:\\n\\n ```\\n | | |\\n | --- | --- |\\n | 1 | |\\n ```\\n* Mark an element as", - "title": "Features | DevRev | Docs" + "id": "ART-17228_KNOWLEDGE_NODE-8", + "text": "inside a given field.\\nThey represent data that consists of multiple elements belonging together (like a phone number or address) but doesn\\xe2\\x80\\x99t form its own record with identity.\\n\\nThese are helpful when the whole struct is optional/nullable, but some of its fields are required, providing a cleaner representation than flattening it.\\nExample:\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | { |\\n| 2 | \"address\": { |\\n| 3 | \"country\": \"US\", |\\n| 4 | \"state\": \"TX\", |\\n| 5 | \"city\": \"Austin\", |\\n|", + "title": "Common issues | DevRev | Docs" }, { - "id": "ART-17230_KNOWLEDGE_NODE-5", - "text": "about products, services, and processes.\\nThey support both Markdown and HTML formats.\\n\\nArticles can include mentions to artifacts and other articles. Inline attachments must map to artifacts,\\nand article links must map to articles.\\n\\n### Managing permissions\\n\\nArticle permissions are managed through the `shared_with` field, which can reference users, groups, and platform groups.\\nRefer to the [permissions](/public/airsync/data-model/permissions) for more details.\\n\\n### Inline", - "title": "Rich text fields | DevRev | Docs" + "id": "ART-15487_KNOWLEDGE_NODE-35", + "text": "groupable. Requires `is_filterable` to be true.\\n* `order`: The order in which the field appears in the side panel.\\n* `is_read_only`: Whether the field is read-only in the UI. Once the object is created, this\\n field cannot be updated in the UI.\\n* `group_name`: The group title under which field(s) appear in the side panel. In the\\n example below, the fields are grouped under groups titled **Group 1** and **Group 2**.\\n\\n ![]()\\n* `unit`: The unit for the field. For example, days, kg. The", + "title": "Object customization | DevRev | Docs" }, { - "id": "ART-17230_KNOWLEDGE_NODE-14", - "text": "\\xe2\\x80\\x9cdocuments\\xe2\\x80\\x9d).\\nThe platform replaces the mention with the corresponding DevRev article ID and adds the appropriate href attribute.\\n\\nWas this page helpful?\\n\\nYesNo\\n\\n[Previous](/airsync/supported-object-types)[#### Permissions\\n\\nNext](/airsync/data-model/permissions)[Built with](https://buildwithfern.com/?utm_campaign=buildWith&utm_medium=docs&utm_source=developer.devrev.ai)'", - "title": "Rich text fields | DevRev | Docs" + "id": "ART-3235_KNOWLEDGE_NODE-25", + "text": "one.\\n\\nInstallation\\n------------\\n\\nInstall the [Reported by Enricher](https://marketplace.devrev.ai/ticket-reported-by) from DevRev marketplace.\\n\\nConfiguration\\n-------------\\n\\nIn the **Configuration** tab, the following settings are available:\\n\\n* **Custom Email Field**: Specify the backend name of the custom field where the email is entered when creating a ticket.\\n* **Default Account**: Select the account to which new customers should be linked if they do not already exist in the", + "title": "Reported by enricher | Automate | Snap-ins | DevRev" }, { - "id": "ART-12453_KNOWLEDGE_NODE-23", - "text": "provides an auto-masking feature that masks data before sending to the server. Input views such as text fields, text views, and web views are automatically masked.\\n\\nWhile the auto-masking feature may be sufficient for most situations, you can manually mark additional views as sensitive using the following method:\\n\\n[code]\\n\\n 1| DevRev.markSensitiveViews(_:) \\n ---|---\\n[/code] \\n \\nIf any previously masked views need to be unmasked, you can use the following method:\\n\\n[code]\\n\\n", - "title": "Features \u2014 DevRev | Docs" + "id": "ART-1508_KNOWLEDGE_NODE-11", + "text": "\"updated\": { |\\n| 180 | \"field_deltas\": [ |\\n| 181 | { |\\n| 182 | \"field_descriptor\": { |\\n| 183 | \"description\": {}, |\\n| 184 | \"is_filterable\": {}, |\\n| 185 | \"is_immutable\": {}, |\\n| 186 | \"is_pii\": {}, |\\n| 187 | \"is_required\": {}, |\\n| 188 | \"mfz\": {}, |\\n| 189 | \"name\": {}, |\\n| 190 | \"oasis\": {}, |\\n| 191 | \"origin\": {}, |\\n| 192 | \"ui\": {}, |\\n| 193 | \"default_value\": {} |\\n| 194 | }, |\\n| 195 | \"name\": \"string\", |\\n| 196 | \"new_value\": { |\\n| 197 | \"fields\": {} |\\n| 198 | }, |\\n| 199 |", + "title": "Export Conversations | DevRev | Docs" }, { - "id": "ART-12456_KNOWLEDGE_NODE-18", - "text": "protect sensitive data, the DevRev SDK provides an auto-masking feature that masks data before sending to the server. Input views such as text fields, text views, and web views are automatically masked.\\n\\nWhile the auto-masking feature may be sufficient for most situations, you can manually mark additional views as sensitive using the following method:\\n\\n[code]\\n\\n 1| DevRev.markSensitiveViews(tags: any[]) \\n ---|---\\n[/code] \\n \\nIf any previously masked views need to be unmasked,", - "title": "Features \u2014 DevRev | Docs" + "id": "ART-996_KNOWLEDGE_NODE-14", + "text": "api_visibility: public\\n api_required: true\\n summary: true # NOTE: `title` included in summary\\n---\\n- name: severity\\n devrev_field_type: legacy_enum\\n devrev_enum:\\n - blocker\\n - high\\n - medium\\n - low\\n is_required: true\\n description: Severity of the ticket\\n gateway:\\n api_visibility: public\\n is_filterable: true\\n summary: true # NOTE: `severity` included in summary\\n\\n\\nDon\\xe2\\x80\\x99t\\nDon\\xe2\\x80\\x99t set all fields to summary: true\\n\\n - name:", + "title": "An Example Object Model Style Guide (our actual style guide)" }, { - "id": "ART-17230_KNOWLEDGE_NODE-7", - "text": "src=\"don:core:dvrv-us-1:devo/0:artifact/1\" alt=\"Alt Text\"/> |\\n```\\n\\nThe following Markdown example shows an inline attachment:\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | ![Alt Text](don:core:dvrv-us-1:devo/0:artifact/1) |\\n```\\n\\nLet\\xe2\\x80\\x99s say the content of your external system looks like this:\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 |

|\\n| 2 | This is an article with one image. |\\n| 3 |

|\\n| 4 |

|\\n| 5 | Integrations > Imports**.\\n2. Select the import you want to view.\\n3. Click on the context menu (\\xe2\\x8b\\xae) and select View Report.\\n\\n### Periodic sync\\n\\nAfter successfully importing to DevRev, you have the option to enable a periodic sync. This allows for automatic synchronization with DevRev on a regular basis. By default, the sync occurs once an hour.\\n\\nTo configure periodic sync, follow these steps:\\n\\n1. Go to **Settings >", + "title": "Dropbox AirSync | AirSync | Snap-ins | DevRev" }, { - "id": "ART-1963_KNOWLEDGE_NODE-4", - "text": "insights](/docs/dashboards/conversation-insights)\\n - [Conversation-SLA Analytics](/docs/dashboards/conversation-sla-analytics)\\n - [Conversation-Team Performance](/docs/dashboards/conversation-team-performance)\\n - [Ticket insights](/docs/dashboards/ticket-insights)\\n - [Ticket-SLA Analytics](/docs/dashboards/ticket-sla-analytics)\\n - [Ticket-Team Performance](/docs/dashboards/ticket-team-performance)\\n + [Conversations](/docs/product/conversation)\\n\\n - [Conversation to", - "title": "Accessing DevRev | Computer by DevRev | DevRev" + "id": "ART-2045_KNOWLEDGE_NODE-31", + "text": "several options to manage and sync your data:\\n\\n* **Sync to DevRev:** Synchronize new items created and modifications made in the external source to corresponding items in DevRev.\\n* **Sync to External Source:** Synchronize new items created in DevRev and modifications made in DevRev to the external source.\\n* **Periodic Sync:** Enable automatic periodic sync to keep data updated between DevRev and the external source.\\n* **View Report:** Access detailed information about the initial import", + "title": "AirSync | Snap-ins | DevRev" }, { - "id": "ART-2046_KNOWLEDGE_NODE-15", - "text": "[Operational SLA Metrics](/docs/automations/operational-sla-metrics)\\n - [Custom field migration](/docs/automations/custom-field-migration)\\n - [Slack scraper](/docs/automations/slack-scraper)\\n - [Slack Broadcaster](/docs/automations/slack-broadcaster)\\n - [Reported by enricher](/docs/automations/ticket-reported-by)\\n - [Ticket approval workflow](/docs/automations/ticket-approval-workflow)\\n - [Ticket linked issues comment", - "title": "DevRev for Jira app | Jira Software AirSync | AirSync | Snap-ins | DevRev" + "id": "ART-2055_KNOWLEDGE_NODE-30", + "text": "modifications made in Linear to the corresponding work item in\\n DevRev.\\n + Create new work items in DevRev for any new issues created in Linear after\\n the last sync or import.\\n* [Sync DevRev to Snap-ins](#sync-to-linear)\\n + Write any modifications made in DevRev to the corresponding work item in\\n Linear.\\n + Create new work items in Linear for any new issues created in DevRev after the last sync or import.\\n* View report\\n + View details of the initial import and any syncs", + "title": "Linear AirSync | AirSync | Snap-ins | DevRev" }, { - "id": "ART-15792_KNOWLEDGE_NODE-9", - "text": "information sharing and reporting by converging support, product and user data in one shared view.\\n\\nAutomated knowledge base management: AI agents remember successful resolutions and instantly apply them to future issues, reducing customer wait time.\\n\\nSource: [DevRev Support](https://devrev.ai/support)BuildWhat is DevRev Build?\\n\\nDevRev Build is a full-featured product development platform built for modern businesses and trusted by leading organizations\\n\\nKey Features:\\n\\nAuto-generate", - "title": "DevRev Products and Agents" + "id": "ART-16805_KNOWLEDGE_NODE-34", + "text": "Imports**.\\n2. Select the import you want to view.\\n3. Click on the context menu (\\xe2\\x8b\\xae) and select View Report.\\n\\n### Periodic sync\\n\\nAfter successfully importing to DevRev, you have the option to enable a periodic sync. This allows for automatic synchronization with DevRev on a regular basis. By default, the sync occurs once an hour, but can be configured for intervals from 5 minutes to 1 week.\\n\\nTo configure periodic sync, follow these steps:\\n\\n1. Go to **Settings > Integrations >", + "title": "Articulate Reach 360 AirSync | AirSync | Snap-ins | DevRev" }, { - "id": "ART-1952_KNOWLEDGE_NODE-27", - "text": "bring in data from other sources as well.\\n\\nDiscover\\n--------\\n\\nTo get started, click the \\xe2\\x9a\\xa1 button on a vista. The following options are available:\\n\\n* Create New Report\\n* View Past Reports: Created by me or shared with me\\n\\nYou can also search for reports and find more on the **Explore** page.\\n\\n![]()\\n\\n### Create\\n\\nYou can create your own reports by adding a name, description, and creating widgets. Here, you'll also be able to preview your report and make any necessary", - "title": "Vista Reports | Vistas | Computer by DevRev | DevRev" + "id": "ART-15506_KNOWLEDGE_NODE-16", + "text": "request details and timestamp. |\\n\\n### How resolution works\\n\\nWhen you send object information to DevRev, the system automatically creates or finds existing contacts, accounts, and workspaces.\\n\\nDevRev offers three ways to structure your customer\\xe2\\x80\\x99s data:\\n\\n| Hierarchy Type | Documents Created | What to Include | Use Case |\\n| --- | --- | --- | --- |\\n| **Single-level** | Contacts only | Only user information | Recommended for most B2C cases |\\n| **Two-level** | Accounts and", + "title": "Identify your users with Plug | DevRev | Docs" }, { - "id": "ART-3208_KNOWLEDGE_NODE-31", - "text": "Select the import you want to view.\\n3. Select the context menu (\\xe2\\x8b\\xae) > **View Report**.\\n\\n### Periodic sync\\n\\nAfter successfully importing to DevRev, you have the option to enable a periodic sync. This allows for automatic synchronization with DevRev on a regular basis. By default, the sync occurs once an hour.\\n\\nTo configure periodic sync, follow these steps:\\n\\n1. Go to **Settings** > **Integrations** > **AirSyncs**.\\n2. Locate the previously imported project.\\n3. Select the", - "title": "DevRev AirSync | AirSync | Snap-ins | DevRev" + "id": "ART-2002_KNOWLEDGE_NODE-31", + "text": "**Group** conditions across various vistas in DevRev to track specific work, capacity, and more.\\n\\nYou can add custom attributes to opportunities to track additional information. For more information on custom attributes, see [object customization](./object-customization).\\n\\n### External reference\\n\\nWhile ingesting customer identity into DevRev, customer information coming across channels must be matched to the same record. \\nFor example, a customer record created by you using APIs should", + "title": "Contacts | Computer for Growth Teams | DevRev" }, { - "id": "ART-2046_KNOWLEDGE_NODE-4", - "text": "analytics](/docs/product/support-analytics)\\n\\n - [Conversation insights](/docs/dashboards/conversation-insights)\\n - [Conversation-SLA Analytics](/docs/dashboards/conversation-sla-analytics)\\n - [Conversation-Team Performance](/docs/dashboards/conversation-team-performance)\\n - [Ticket insights](/docs/dashboards/ticket-insights)\\n - [Ticket-SLA Analytics](/docs/dashboards/ticket-sla-analytics)\\n - [Ticket-Team Performance](/docs/dashboards/ticket-team-performance)\\n +", - "title": "DevRev for Jira app | Jira Software AirSync | AirSync | Snap-ins | DevRev" + "id": "ART-1566_KNOWLEDGE_NODE-321", + "text": "11 \" display_id \" : \" display_id \" , 12 \" evaluation_period \" : \" monthly \" , 13 \" modified_date \" : \" 2023-01-01T12:00:00Z \" , 14 \" policies \" : [ 15 { 16 \" key \" : \" value \" 17 } 18 ] , 19 \" sla_type \" : \" external \" 20 } 21 }\\nAPI Reference product-usage Metrics Devrev Ingest.\\n\\nPOST https://api.devrev.ai / metrics.devrev.ingest\\n\\nIngest endpoint for DevRev metrics data from clients.\\n\\nRequest.\\n\\nThis endpoint expects an object.\\nmetrics list of objects Required\\n\\nMetrics data received", + "title": "Transition (Beta) \u2014 DevRev | Docs" }, { - "id": "ART-738_KNOWLEDGE_NODE-8", - "text": "purchase a product, you consider the need, cost, runway, future needs, etc.\\n\\nNow, say you want to prioritize which work you should focus on and deliver in the next sprint. You\\xe2\\x80\\x99d need information about other items in-flight, staff workload, customer impact of items, dependent opportunities, and a lot of additional data.\\n\\nWith DevRev, we have the full context and can use that to feed into the models. With the other point systems, you\\xe2\\x80\\x99d need to consolidate somewhere", - "title": "DevRev | Built for AI (not by AI... yet)" + "id": "ART-1305_KNOWLEDGE_NODE-276", + "text": "endpoint for DevRev metrics data from clients.\\nRequest.\\n\\nThis endpoint expects an object.\\nmetrics list of objects Required\\nMetrics data received from Dev orgs.\\nShow 5 properties\\nAPI Reference product-usage Uoms Count.\\n\\nGET https:// api.devrev.ai / uoms.count\\nCounts the number of Unit of Measurements based on the given filters.\\nQuery parameters.\\n\\naggregation_types enum Optional\\nList of aggregation types for filtering list of UOMs.\\nShow 8 enum values\\nids string Optional\\nList of", + "title": "Get Post \u2014 DevRev | Docs" }, { - "id": "ART-15687_KNOWLEDGE_NODE-26", - "text": "For example, to find opportunities data, search for opportunity and select the dim\\\\_opportunity dataset.\\n4. Write a SQL query and run it.\\n\\nTesting your query in Notebook ensures you have the correct dataset for your visualization.\\n\\n* **Access the widget builder**:\\n\\nGo to the widget builder by modifying your DevRev workspace URL. For example, your\\\\_workspace\\\\_slug/widget-preview.\\nThe builder provides a boilerplate code that you can modify.\\n\\n![]()\\n\\n* **Define your dataset (Oasis", - "title": "Dashboards | Computer by DevRev | DevRev" + "id": "ART-1834_KNOWLEDGE_NODE-269", + "text": "endpoint for DevRev metrics data from clients.\\nRequest.\\n\\nThis endpoint expects an object.\\nmetrics list of objects Required\\nMetrics data received from Dev orgs.\\nShow 5 properties\\nAPI Reference product-usage Uoms Count.\\n\\nGET https:// api.devrev.ai / uoms.count\\nCounts the number of Unit of Measurements based on the given filters.\\nQuery parameters.\\n\\naggregation_types enum Optional\\nList of aggregation types for filtering list of UOMs.\\nShow 8 enum values\\nids string Optional\\nList of", + "title": "Delete \u2014 DevRev | Docs" }, { - "id": "ART-15792_KNOWLEDGE_NODE-11", - "text": "to maintain visibility of resource allocation even as you scale\\n\\nProduct 360 Analytics: Enhance customer experience, product velocity, and developer productivity with robust Product 360 analytics\\n\\nCustomer-focused Development: Make development customer-focused with sprints that adapt to customer requirements\\n\\nSource: [DevRev Build](https://devrev.ai/build)User ObservabilityWhat is DevRev User Observability?\\n\\nDevRev User Observability helps you gain a clear window into your user journeys", - "title": "DevRev Products and Agents" + "id": "ART-1824_KNOWLEDGE_NODE-269", + "text": "endpoint for DevRev metrics data from clients.\\nRequest.\\n\\nThis endpoint expects an object.\\nmetrics list of objects Required\\nMetrics data received from Dev orgs.\\nShow 5 properties\\nAPI Reference product-usage Uoms Count.\\n\\nGET https:// api.devrev.ai / uoms.count\\nCounts the number of Unit of Measurements based on the given filters.\\nQuery parameters.\\n\\naggregation_types enum Optional\\nList of aggregation types for filtering list of UOMs.\\nShow 8 enum values\\nids string Optional\\nList of", + "title": "Delete \u2014 DevRev | Docs" } ] }, @@ -619,55 +619,55 @@ "query_id": "ed5940c0-01b1-45bc-8489-dccca3575588", "query": "populate Timeline Comment Created trigger for a ticket object", "retrievals": [ + { + "id": "ART-1485_KNOWLEDGE_NODE-10", + "text": "invoke the snap-in, two distinct triggers are implemented:\\n\\n 1. **Creation of work item** : This trigger is activated when new objects of type **Issue** or **Ticket** are created in DevRev.\\n\\n 2. **Text command** : This manual trigger is achieved by utilizing a slash command in the **Discussions** tab of the objects that support this feature.\\n\\n#### Action\\n\\nTo implement the desired action of adding a comment to the object timeline, it is essential to identify the appropriate [API] for", + "title": "Snap-in triggered by a DevRev event \u2014 DevRev | Docs" + }, { "id": "ART-1277_KNOWLEDGE_NODE-6", - "text": "objects of type\\n **Issue** or **Ticket** are created in DevRev.\\n2. **Text command**: This manual trigger is achieved by utilizing a slash\\n command in the **Discussions** tab of the objects that support this feature.\\n\\n#### Action\\n\\nTo implement the desired action of adding a comment to the object timeline, it\\nis essential to identify the appropriate [API]\\nfor this task. In this scenario, the `/timeline-entries.create` API is the\\ndesignated choice for executing the action of adding a", + "text": "objects of type\\n **Issue** or **Ticket** are created in DevRev.\\n2. **Text command**: This manual trigger is achieved by utilizing a slash\\n command in the **Discussions** tab of the objects that support this feature.\\n\\n#### Action\\n\\nTo implement the desired action of adding a comment to the object timeline, it\\nis essential to identify the appropriate [API]\\nfor this task. In this scenario, the `/timeline-entries.create` API is the\\ndesignated choice for executing the action of adding a", "title": "Snap-in triggered by a DevRev event | DevRev | Docs" }, { - "id": "ART-1265_KNOWLEDGE_NODE-9", - "text": "timeline of an issue/ticket using the `timeline-entries.create` API with different visibilities. You can now use this to create comments on timeline using automation or manually based on your use case.\\n\\nWas this page helpful?\\n\\nYesNo\\n\\n[Previous](/guides/webhooks)[#### Object customization\\n\\nNext](/guides/object-customization)[Built with](https://buildwithfern.com/?utm_campaign=buildWith&utm_medium=docs&utm_source=developer.devrev.ai)\\n\\n![]()'", - "title": "Restricted messages on a timeline | DevRev | Docs" + "id": "ART-1435_KNOWLEDGE_NODE-2", + "text": "\"Content-Type: application/json\" \\\\ \\n >| -d \\'{ \\n >| \"id\": \"don:core:dvrv-us-1:devo/example:ticket/123:comment/comment-id\" \\n >| }\\'\\n[/code] \\n \\nTry it\\n\\n200timelineEntriesGetPostExample\\n\\n[code]\\n\\n 1| { \\n ---|--- \\n 2| \"timeline_entry\": { \\n 3| \"created_by\": { \\n 4| \"display_id\": \"foo\", \\n 5| \"id\": \"foo\", \\n 6| \"display_name\": \"foo\", \\n 7| \"display_picture\": { \\n 8| \"display_id\": \"foo\", \\n", + "title": "Get Timeline Entry (POST) \u2014 DevRev | Docs" }, { "id": "ART-1425_KNOWLEDGE_NODE-2", - "text": "id=don:core:dvrv-us-1:devo/example:ticket/123:comment/comment-id\\n[/code] \\n \\nTry it\\n\\n200getExample\\n\\n[code]\\n\\n 1| { \\n ---|--- \\n 2| \"timeline_entry\": { \\n 3| \"created_by\": { \\n 4| \"display_id\": \"foo\", \\n 5| \"id\": \"foo\", \\n 6| \"display_name\": \"foo\", \\n 7| \"display_picture\": { \\n 8| \"display_id\": \"foo\", \\n 9| \"id\": \"foo\", \\n 10| \"file\": { \\n 11| \"type\": \"foo\", \\n 12|", + "text": "id=don:core:dvrv-us-1:devo/example:ticket/123:comment/comment-id\\n[/code] \\n \\nTry it\\n\\n200getExample\\n\\n[code]\\n\\n 1| { \\n ---|--- \\n 2| \"timeline_entry\": { \\n 3| \"created_by\": { \\n 4| \"display_id\": \"foo\", \\n 5| \"id\": \"foo\", \\n 6| \"display_name\": \"foo\", \\n 7| \"display_picture\": { \\n 8| \"display_id\": \"foo\", \\n 9| \"id\": \"foo\", \\n 10| \"file\": { \\n 11| \"type\": \"foo\", \\n 12|", "title": "Get Timeline Entry \u2014 DevRev | Docs" }, { "id": "ART-1471_KNOWLEDGE_NODE-9", - "text": "}\\n[/code] \\n \\nYou can check the object to which you sent a message in the UI. It\\xe2\\x80\\x99s visible to the creator and the users you added in `private_to`.\\n\\n## Summary\\n\\nIn this tutorial, you learned how to post a comment on the timeline of an issue/ticket using the `timeline-entries.create` API with different visibilities. You can now use this to create comments on timeline using automation or manually based on your use case.\\n\\nWas this page helpful?YesNo\\n\\n[SDKsUp", + "text": "}\\n[/code] \\n \\nYou can check the object to which you sent a message in the UI. It\\xe2\\x80\\x99s visible to the creator and the users you added in `private_to`.\\n\\n## Summary\\n\\nIn this tutorial, you learned how to post a comment on the timeline of an issue/ticket using the `timeline-entries.create` API with different visibilities. You can now use this to create comments on timeline using automation or manually based on your use case.\\n\\nWas this page helpful?YesNo\\n\\n[SDKsUp", "title": "Restricted messages on a timeline \u2014 DevRev | Docs" }, { - "id": "ART-4184_KNOWLEDGE_NODE-28", - "text": "relationships.\\n\\n![]()\\n\\n* Comments synchronize only between directly linked items.\\n* Editing a comment after synchronization does not update the synchronized copies.\\n* Ticket threads are not fully supported yet. DevRev supports only one level of nesting; threaded comments in tickets are supported as flat items.\\n\\n[PreviousTicket approval workflow](/docs/automations/ticket-approval-workflow)[NextSlack message agent](/docs/automations/slack-message-agent)\\n\\n#### On this page\\n\\n* [Key", - "title": "Ticket linked issues comment sync | Automate | Snap-ins | DevRev" - }, - { - "id": "ART-1227_KNOWLEDGE_NODE-6", - "text": "|\\n```\\n\\nCreates a new entry on an object\\'s timeline.\\n\\n### Headers\\n\\nAuthorizationstringRequired\\n\\nBearer authentication of the form `Bearer `, where token is your auth token.\\n\\n### Request\\n\\nThis endpoint expects an object.\\n\\ntimeline\\\\_commentobjectRequired\\n\\nShow 9 properties\\n\\n### Response\\n\\nThe response to creating a timeline entry for an object.\\n\\ntimeline\\\\_entryobject\\n\\nShow 1 variants\\n\\n### Errors\\n\\n400\\n\\nBad Request Error\\n\\n401\\n\\nUnauthorized", - "title": "Create Timeline Entry | DevRev | Docs" + "id": "ART-1265_KNOWLEDGE_NODE-9", + "text": "timeline of an issue/ticket using the `timeline-entries.create` API with different visibilities. You can now use this to create comments on timeline using automation or manually based on your use case.\\n\\nWas this page helpful?\\n\\nYesNo\\n\\n[Previous](/guides/webhooks)[#### Object customization\\n\\nNext](/guides/object-customization)[Built with](https://buildwithfern.com/?utm_campaign=buildWith&utm_medium=docs&utm_source=developer.devrev.ai)\\n\\n![]()'", + "title": "Restricted messages on a timeline | DevRev | Docs" }, { - "id": "ART-4184_KNOWLEDGE_NODE-13", - "text": "creator](/docs/automations/smart-issue-creator)\\n - [Set user preference for group](/docs/automations/set-user-preference)\\n - [SLA status change Slack notifier](/docs/automations/sla-change-notifier)\\n - [Slash commands](/docs/automations/slash-commands)\\n - [Spam Shield](/docs/automations/spam-shield)\\n - [Subtype Migration](/docs/automations/subtype-migration)\\n - [Ticket age in engineering](/docs/automations/ticket-age-in-engineering)\\n - [Ticket issue field", - "title": "Ticket linked issues comment sync | Automate | Snap-ins | DevRev" + "id": "ART-1229_KNOWLEDGE_NODE-1", + "text": "\"Authorization: Bearer \" \\\\ |\\n| > | --data-urlencode id=don:core:dvrv-us-1:devo/example:ticket/123:comment/comment-id |\\n```\\n\\n[Try it](/api-reference/timeline-entries/get?explorer=true)\\n\\n200Retrieved\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | { |\\n| 2 | \"timeline_entry\": { |\\n| 3 | \"created_by\": { |\\n| 4 | \"display_id\": \"string\", |\\n| 5 | \"id\": \"string\", |\\n| 6 | \"display_name\": \"string\", |\\n| 7 | \"display_picture\": { |\\n| 8 | \"display_id\": \"string\", |\\n| 9 | \"id\": \"string\", |\\n| 10 |", + "title": "Get Timeline Entry | DevRev | Docs" }, { - "id": "ART-4184_KNOWLEDGE_NODE-24", - "text": "[Product demos](/docs/DevRevU/demos)\\n\\nOn this page\\n\\n* [Key features](#key-features)\\n* [Installation and configuration](#installation-and-configuration)\\n* [Prerequisites](#prerequisites)\\n* [Setup steps](#setup-steps)\\n\\n1. [Documentation](/docs)\\n3. [Snap-ins](/docs/snapins)\\n[Automate](/docs/automate)\\n[Ticket linked issues comment sync](/docs/automations/ticket-linked-issues-comment-sync)\\n\\nTicket linked issues comment sync\\n=================================\\n\\nThe **Ticket Linked", - "title": "Ticket linked issues comment sync | Automate | Snap-ins | DevRev" + "id": "ART-1230_KNOWLEDGE_NODE-1", + "text": "https://api.devrev.ai/timeline-entries.get \\\\ |\\n| > | -H \"Authorization: Bearer \" \\\\ |\\n| > | -H \"Content-Type: application/json\" \\\\ |\\n| > | -d \\'{ |\\n| > | \"id\": \"don:core:dvrv-us-1:devo/example:ticket/123:comment/comment-id\" |\\n| > | }\\' |\\n```\\n\\n[Try it](/api-reference/timeline-entries/get-post?explorer=true)\\n\\n200Successful\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | { |\\n| 2 | \"timeline_entry\": { |\\n| 3 | \"created_by\": { |\\n| 4 | \"display_id\": \"string\", |\\n| 5 | \"id\": \"string\", |\\n| 6", + "title": "Get Timeline Entry (POST) | DevRev | Docs" }, { - "id": "ART-1227_KNOWLEDGE_NODE-1", - "text": "\\\\ |\\n| > | -H \"Authorization: Bearer \" \\\\ |\\n| > | -H \"Content-Type: application/json\" \\\\ |\\n| > | -d \\'{}\\' |\\n```\\n\\n[Try it](/api-reference/timeline-entries/create?explorer=true)\\n\\n201Created\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | { |\\n| 2 | \"timeline_entry\": { |\\n| 3 | \"created_by\": { |\\n| 4 | \"display_id\": \"string\", |\\n| 5 | \"id\": \"string\", |\\n| 6 | \"display_name\": \"string\", |\\n| 7 | \"display_picture\": { |\\n| 8 | \"display_id\": \"string\", |\\n| 9 | \"id\": \"string\", |\\n| 10 | \"file\": {", - "title": "Create Timeline Entry | DevRev | Docs" + "id": "ART-1490_KNOWLEDGE_NODE-42", + "text": "\"don:core::devo/:ticket/123:timeline_event/\" \\n 356| }, \\n 357| \"timeline_entry_updated\": { \\n 358| \"entry\": { \\n 359| \"created_by\": {}, \\n 360| \"created_date\": \"2023-01-01T12:00:00.000Z\", \\n 361| \"display_id\": \"string\", \\n 362| \"id\": \"string\", \\n 363| \"modified_by\": {}, \\n 364| \"modified_date\": \"2023-01-01T12:00:00.000Z\", \\n 365| \"object\": \"string\", \\n 366|", + "title": "Snap-in manifest \u2014 DevRev | Docs" }, { - "id": "ART-1435_KNOWLEDGE_NODE-2", - "text": "\"Content-Type: application/json\" \\\\ \\n >| -d \\'{ \\n >| \"id\": \"don:core:dvrv-us-1:devo/example:ticket/123:comment/comment-id\" \\n >| }\\'\\n[/code] \\n \\nTry it\\n\\n200timelineEntriesGetPostExample\\n\\n[code]\\n\\n 1| { \\n ---|--- \\n 2| \"timeline_entry\": { \\n 3| \"created_by\": { \\n 4| \"display_id\": \"foo\", \\n 5| \"id\": \"foo\", \\n 6| \"display_name\": \"foo\", \\n 7| \"display_picture\": { \\n 8| \"display_id\": \"foo\", \\n", - "title": "Get Timeline Entry (POST) \u2014 DevRev | Docs" + "id": "ART-15435_KNOWLEDGE_NODE-1", + "text": "\"Authorization: Bearer \" \\\\ |\\n| > | -H \"Content-Type: application/json\" \\\\ |\\n| > | -d \\'{ |\\n| > | \"emoji\": \"string\", |\\n| > | \"object\": \"don:core:dvrv-us-1:devo/example:ticket/123:comment/comment-id\" |\\n| > | }\\' |\\n```\\n\\n[Try it](/api-reference/timeline-entries/reactions-list-post?explorer=true)\\n\\n200Successful\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | { |\\n| 2 | \"reactors\": [ |\\n| 3 | { |\\n| 4 | \"display_id\": \"string\", |\\n| 5 | \"id\": \"string\", |\\n| 6 | \"display_name\": \"string\", |\\n| 7", + "title": "List Reactions (POST) | DevRev | Docs" } ] }, @@ -676,54 +676,54 @@ "query": "DevRev Bot groups created from airdrops", "retrievals": [ { - "id": "ART-1591_KNOWLEDGE_NODE-149", - "text": "groups based on the group type.\\nAllowed values: dynamic static\\ningestion_source \"airdrop\" or \"scim\" Optional\\nFilter groups by ingestion source(s).\\nAllowed values: airdrop scim\\nis_default boolean Optional\\nWhether to fetch default or custom groups.\\nlimit integer Optional\\nThe maximum number of groups to return. The default is \\'50\\'.\\nmember_type \"dev_user\" or \"rev_user\" Optional\\nFilters the groups on basis of member type.\\nAllowed values: dev_user rev_user\\nmode \"after\" or \"before\"", - "title": "Create \u2014 DevRev | Docs" + "id": "ART-1545_KNOWLEDGE_NODE-233", + "text": "https://api.devrev.ai / groups.list\\n\\nLists the available groups.\\n\\nRequest.\\n\\nThis endpoint expects an object.\\ncursor string Optional\\n\\nThe cursor to resume iteration from. If not provided, then iteration starts from the beginning.\\n\\ngroup_type list of \"dynamic\" or \"static\" Optional\\nAllowed values: dynamic static\\n\\nFilters the groups based on the group type.\\n\\ningestion_source list of \"airdrop\" or \"scim\" Optional\\nAllowed values: airdrop scim\\n\\nFilter groups by ingestion", + "title": "Create (Beta) \u2014 DevRev | Docs" }, { - "id": "ART-1605_KNOWLEDGE_NODE-149", - "text": "groups based on the group type.\\nAllowed values: dynamic static\\ningestion_source \"airdrop\" or \"scim\" Optional\\nFilter groups by ingestion source(s).\\nAllowed values: airdrop scim\\nis_default boolean Optional\\nWhether to fetch default or custom groups.\\nlimit integer Optional\\nThe maximum number of groups to return. The default is \\'50\\'.\\nmember_type \"dev_user\" or \"rev_user\" Optional\\nFilters the groups on basis of member type.\\nAllowed values: dev_user rev_user\\nmode \"after\" or \"before\"", - "title": "Create \u2014 DevRev | Docs" + "id": "ART-1560_KNOWLEDGE_NODE-233", + "text": "https://api.devrev.ai / groups.list\\n\\nLists the available groups.\\n\\nRequest.\\n\\nThis endpoint expects an object.\\ncursor string Optional\\n\\nThe cursor to resume iteration from. If not provided, then iteration starts from the beginning.\\n\\ngroup_type list of \"dynamic\" or \"static\" Optional\\nAllowed values: dynamic static\\n\\nFilters the groups based on the group type.\\n\\ningestion_source list of \"airdrop\" or \"scim\" Optional\\nAllowed values: airdrop scim\\n\\nFilter groups by ingestion", + "title": "Assign (Beta) \u2014 DevRev | Docs" }, { - "id": "ART-1649_KNOWLEDGE_NODE-149", - "text": "groups based on the group type.\\nAllowed values: dynamic static\\ningestion_source \"airdrop\" or \"scim\" Optional\\nFilter groups by ingestion source(s).\\nAllowed values: airdrop scim\\nis_default boolean Optional\\nWhether to fetch default or custom groups.\\nlimit integer Optional\\nThe maximum number of groups to return. The default is \\'50\\'.\\nmember_type \"dev_user\" or \"rev_user\" Optional\\nFilters the groups on basis of member type.\\nAllowed values: dev_user rev_user\\nmode \"after\" or \"before\"", - "title": "Create \u2014 DevRev | Docs" + "id": "ART-1566_KNOWLEDGE_NODE-233", + "text": "https://api.devrev.ai / groups.list\\n\\nLists the available groups.\\n\\nRequest.\\n\\nThis endpoint expects an object.\\ncursor string Optional\\n\\nThe cursor to resume iteration from. If not provided, then iteration starts from the beginning.\\n\\ngroup_type list of \"dynamic\" or \"static\" Optional\\nAllowed values: dynamic static\\n\\nFilters the groups based on the group type.\\n\\ningestion_source list of \"airdrop\" or \"scim\" Optional\\nAllowed values: airdrop scim\\n\\nFilter groups by ingestion", + "title": "Transition (Beta) \u2014 DevRev | Docs" }, { - "id": "ART-1651_KNOWLEDGE_NODE-149", - "text": "groups based on the group type.\\nAllowed values: dynamic static\\ningestion_source \"airdrop\" or \"scim\" Optional\\nFilter groups by ingestion source(s).\\nAllowed values: airdrop scim\\nis_default boolean Optional\\nWhether to fetch default or custom groups.\\nlimit integer Optional\\nThe maximum number of groups to return. The default is \\'50\\'.\\nmember_type \"dev_user\" or \"rev_user\" Optional\\nFilters the groups on basis of member type.\\nAllowed values: dev_user rev_user\\nmode \"after\" or \"before\"", - "title": "Create \u2014 DevRev | Docs" + "id": "ART-1562_KNOWLEDGE_NODE-233", + "text": "https://api.devrev.ai / groups.list\\n\\nLists the available groups.\\n\\nRequest.\\n\\nThis endpoint expects an object.\\ncursor string Optional\\n\\nThe cursor to resume iteration from. If not provided, then iteration starts from the beginning.\\n\\ngroup_type list of \"dynamic\" or \"static\" Optional\\nAllowed values: dynamic static\\n\\nFilters the groups based on the group type.\\n\\ningestion_source list of \"airdrop\" or \"scim\" Optional\\nAllowed values: airdrop scim\\n\\nFilter groups by ingestion", + "title": "Get (Beta) \u2014 DevRev | Docs" }, { - "id": "ART-1822_KNOWLEDGE_NODE-149", - "text": "groups based on the group type.\\nAllowed values: dynamic static\\ningestion_source \"airdrop\" or \"scim\" Optional\\nFilter groups by ingestion source(s).\\nAllowed values: airdrop scim\\nis_default boolean Optional\\nWhether to fetch default or custom groups.\\nlimit integer Optional\\nThe maximum number of groups to return. The default is \\'50\\'.\\nmember_type \"dev_user\" or \"rev_user\" Optional\\nFilters the groups on basis of member type.\\nAllowed values: dev_user rev_user\\nmode \"after\" or \"before\"", - "title": "Create \u2014 DevRev | Docs" + "id": "ART-1549_KNOWLEDGE_NODE-233", + "text": "https://api.devrev.ai / groups.list\\n\\nLists the available groups.\\n\\nRequest.\\n\\nThis endpoint expects an object.\\ncursor string Optional\\n\\nThe cursor to resume iteration from. If not provided, then iteration starts from the beginning.\\n\\ngroup_type list of \"dynamic\" or \"static\" Optional\\nAllowed values: dynamic static\\n\\nFilters the groups based on the group type.\\n\\ningestion_source list of \"airdrop\" or \"scim\" Optional\\nAllowed values: airdrop scim\\n\\nFilter groups by ingestion", + "title": "List Post (Beta) \u2014 DevRev | Docs" }, { - "id": "ART-1832_KNOWLEDGE_NODE-149", - "text": "groups based on the group type.\\nAllowed values: dynamic static\\ningestion_source \"airdrop\" or \"scim\" Optional\\nFilter groups by ingestion source(s).\\nAllowed values: airdrop scim\\nis_default boolean Optional\\nWhether to fetch default or custom groups.\\nlimit integer Optional\\nThe maximum number of groups to return. The default is \\'50\\'.\\nmember_type \"dev_user\" or \"rev_user\" Optional\\nFilters the groups on basis of member type.\\nAllowed values: dev_user rev_user\\nmode \"after\" or \"before\"", - "title": "Create \u2014 DevRev | Docs" + "id": "ART-1543_KNOWLEDGE_NODE-233", + "text": "https://api.devrev.ai / groups.list\\n\\nLists the available groups.\\n\\nRequest.\\n\\nThis endpoint expects an object.\\ncursor string Optional\\n\\nThe cursor to resume iteration from. If not provided, then iteration starts from the beginning.\\n\\ngroup_type list of \"dynamic\" or \"static\" Optional\\nAllowed values: dynamic static\\n\\nFilters the groups based on the group type.\\n\\ningestion_source list of \"airdrop\" or \"scim\" Optional\\nAllowed values: airdrop scim\\n\\nFilter groups by ingestion", + "title": "Metric Definitions List Post (Beta) \u2014 DevRev | Docs" }, { - "id": "ART-1300_KNOWLEDGE_NODE-153", - "text": "iteration starts from the beginning.\\ngroup_type \"dynamic\" or \"static\" Optional\\nFilters the groups based on the group type.\\nAllowed values: dynamic static\\ningestion_source \"airdrop\" or \"scim\" Optional\\nFilter groups by ingestion source(s).\\nAllowed values: airdrop scim\\nis_default boolean Optional\\nWhether to fetch default or custom groups.\\nlimit integer Optional\\nThe maximum number of groups to return. The default is \\'50\\'.\\nmember_type \"dev_user\" or \"rev_user\" Optional\\nFilters the", - "title": "Create \u2014 DevRev | Docs" + "id": "ART-1564_KNOWLEDGE_NODE-233", + "text": "https://api.devrev.ai / groups.list\\n\\nLists the available groups.\\n\\nRequest.\\n\\nThis endpoint expects an object.\\ncursor string Optional\\n\\nThe cursor to resume iteration from. If not provided, then iteration starts from the beginning.\\n\\ngroup_type list of \"dynamic\" or \"static\" Optional\\nAllowed values: dynamic static\\n\\nFilters the groups based on the group type.\\n\\ningestion_source list of \"airdrop\" or \"scim\" Optional\\nAllowed values: airdrop scim\\n\\nFilter groups by ingestion", + "title": "List (Beta) \u2014 DevRev | Docs" }, { - "id": "ART-1637_KNOWLEDGE_NODE-149", - "text": "groups based on the group type.\\nAllowed values: dynamic static\\ningestion_source \"airdrop\" or \"scim\" Optional\\nFilter groups by ingestion source(s).\\nAllowed values: airdrop scim\\nis_default boolean Optional\\nWhether to fetch default or custom groups.\\nlimit integer Optional\\nThe maximum number of groups to return. The default is \\'50\\'.\\nmember_type \"dev_user\" or \"rev_user\" Optional\\nFilters the groups on basis of member type.\\nAllowed values: dev_user rev_user\\nmode \"after\" or \"before\"", - "title": "Delete \u2014 DevRev | Docs" + "id": "ART-1547_KNOWLEDGE_NODE-233", + "text": "https://api.devrev.ai / groups.list\\n\\nLists the available groups.\\n\\nRequest.\\n\\nThis endpoint expects an object.\\ncursor string Optional\\n\\nThe cursor to resume iteration from. If not provided, then iteration starts from the beginning.\\n\\ngroup_type list of \"dynamic\" or \"static\" Optional\\nAllowed values: dynamic static\\n\\nFilters the groups based on the group type.\\n\\ningestion_source list of \"airdrop\" or \"scim\" Optional\\nAllowed values: airdrop scim\\n\\nFilter groups by ingestion", + "title": "Get Post (Beta) \u2014 DevRev | Docs" }, { - "id": "ART-1821_KNOWLEDGE_NODE-149", - "text": "groups based on the group type.\\nAllowed values: dynamic static\\ningestion_source \"airdrop\" or \"scim\" Optional\\nFilter groups by ingestion source(s).\\nAllowed values: airdrop scim\\nis_default boolean Optional\\nWhether to fetch default or custom groups.\\nlimit integer Optional\\nThe maximum number of groups to return. The default is \\'50\\'.\\nmember_type \"dev_user\" or \"rev_user\" Optional\\nFilters the groups on basis of member type.\\nAllowed values: dev_user rev_user\\nmode \"after\" or \"before\"", - "title": "Delete \u2014 DevRev | Docs" + "id": "ART-1558_KNOWLEDGE_NODE-233", + "text": "https://api.devrev.ai / groups.list\\n\\nLists the available groups.\\n\\nRequest.\\n\\nThis endpoint expects an object.\\ncursor string Optional\\n\\nThe cursor to resume iteration from. If not provided, then iteration starts from the beginning.\\n\\ngroup_type list of \"dynamic\" or \"static\" Optional\\nAllowed values: dynamic static\\n\\nFilters the groups based on the group type.\\n\\ningestion_source list of \"airdrop\" or \"scim\" Optional\\nAllowed values: airdrop scim\\n\\nFilter groups by ingestion", + "title": "Metric Definitions List (Beta) \u2014 DevRev | Docs" }, { - "id": "ART-1824_KNOWLEDGE_NODE-149", - "text": "groups based on the group type.\\nAllowed values: dynamic static\\ningestion_source \"airdrop\" or \"scim\" Optional\\nFilter groups by ingestion source(s).\\nAllowed values: airdrop scim\\nis_default boolean Optional\\nWhether to fetch default or custom groups.\\nlimit integer Optional\\nThe maximum number of groups to return. The default is \\'50\\'.\\nmember_type \"dev_user\" or \"rev_user\" Optional\\nFilters the groups on basis of member type.\\nAllowed values: dev_user rev_user\\nmode \"after\" or \"before\"", - "title": "Delete \u2014 DevRev | Docs" + "id": "ART-1551_KNOWLEDGE_NODE-233", + "text": "https://api.devrev.ai / groups.list\\n\\nLists the available groups.\\n\\nRequest.\\n\\nThis endpoint expects an object.\\ncursor string Optional\\n\\nThe cursor to resume iteration from. If not provided, then iteration starts from the beginning.\\n\\ngroup_type list of \"dynamic\" or \"static\" Optional\\nAllowed values: dynamic static\\n\\nFilters the groups based on the group type.\\n\\ningestion_source list of \"airdrop\" or \"scim\" Optional\\nAllowed values: airdrop scim\\n\\nFilter groups by ingestion", + "title": "Update (Beta) \u2014 DevRev | Docs" } ] }, @@ -731,55 +731,55 @@ "query_id": "a15290e1-d40b-4422-b5ea-170576843e89", "query": "SLA for Next Response stop when stage is moved back to Awaiting Customer", "retrievals": [ - { - "id": "ART-1974_KNOWLEDGE_NODE-28", - "text": "transitions from *new* to *waiting on user*. When a customer responds back to support, the stage transitions to *needs response*.\\n\\n Towards the end of the conversation when the resolution is expected to be valid, the customer experience engineer asks the customer to acknowledge their concerns have been resolved. When the customer experience engineer asks this question the stage transitions to *waiting on user*, and if they validate it moves to *needs response* for the customer experience", - "title": "Conversations | Computer for Support Teams | DevRev" - }, { "id": "ART-1979_KNOWLEDGE_NODE-43", - "text": "*awaiting customer response* until the customer responds.\\n\\n In certain scenarios, the customer experience engineer may be able to resolve the customer's concern. If that's the case, they would ask the customer if their resolution has resolved their concern and the stage would move to the *awaiting customer response*. Once the concern is resolved and the customer acknowledges the resolution, the stage may move to *resolved*. If the concern isn't resolved, the stage may change back to *work in", + "text": "*awaiting customer response* until the customer responds.\\n\\n In certain scenarios, the customer experience engineer may be able to resolve the customer's concern. If that's the case, they would ask the customer if their resolution has resolved their concern and the stage would move to the *awaiting customer response*. Once the concern is resolved and the customer acknowledges the resolution, the stage may move to *resolved*. If the concern isn't resolved, the stage may change back to *work in", "title": "Tickets | Computer for Support Teams | DevRev" }, { - "id": "ART-1974_KNOWLEDGE_NODE-32", - "text": "have been completed the stage transitions to *needs response* to bring to the customer experience engineer's attention. Upon review they may put the conversation back on *hold* to re-escalate the item. If the dependencies seem to be resolved the customer experience engineer responds to the customer and the stage transitions to *waiting on user*.\\n\\n**Closed**\\n\\n* *Resolved* (R)\\n\\n The final target stage for conversations. It means that the customer's concerns which led to the conversation", - "title": "Conversations | Computer for Support Teams | DevRev" + "id": "ART-1979_KNOWLEDGE_NODE-45", + "text": "a user. In certain cases where the ticket depends on some fix (issues) the stage may go from *in development* to *awaiting customer response* when the corresponding issues have been resolved and the fix needs to be validated with the user.\\n\\n In certain cases, the customer experience engineer may be able to solve directly (without any required issues) which may change the stage from *work in progress* to *awaiting customer response* to validate they have solved the problem. If either has", + "title": "Tickets | Computer for Support Teams | DevRev" }, { - "id": "ART-1974_KNOWLEDGE_NODE-30", - "text": "stage.\\n* *Needs response* (NR)\\n\\n The customer has responded; the customer experience engineer needs to review the item and respond or resolve the issue if the user requests or validates the fix. When a customer experience engineer responds the stage transitions to *waiting on user*.\\n\\n In certain cases it may be necessary to escalate the item internally where the conversation may depend on tickets, issues, or a response from someone other than themselves. In this case the stage", - "title": "Conversations | Computer for Support Teams | DevRev" + "id": "ART-1979_KNOWLEDGE_NODE-46", + "text": "resolved the customer's concern the stage can move to *resolved*.\\n* Awaiting development (AD)\\n\\n The issues on which the user's concern relies for resolution are planned but not active, when development on the issue begins the stage transitions to *In development*.\\n* In development (ID)\\n\\n The issues on which the user's concern relies for resolution are actively being worked on. Once the development process begins, the stage may go from *in development* to *awaiting customer response* to", + "title": "Tickets | Computer for Support Teams | DevRev" }, { - "id": "ART-1986_KNOWLEDGE_NODE-40", - "text": "conversation moves to any stage except Waiting on User |\\n\\nViewing SLAs\\n------------\\n\\nThe SLA targets applied to a particular conversation can be viewed in the **Inbox** and the **Conversation Detailed** view. For a ticket in any of the ticket vistas.\\n\\nWhen there are two active metrics, vista displays the one closest to the breach. In the case of a conversation where both the first response and full resolution metrics are active, and the first response is due in five minutes but the full", - "title": "Service-level agreement | Computer for Support Teams | DevRev" - }, + "id": "ART-1981_KNOWLEDGE_NODE-32", + "text": "assigned; tickets should be assigned only to revenue team members.\\n\\nManage tickets\\n--------------\\n\\n* Regularly follow up with the customer on any ticket in the *awaiting customer* stage. If no response is forthcoming in a reasonable amount of time as defined by your SLA, mark the ticket as *resolved*.\\n* Critically assess the severity of the ticket according to the impact on the customer\\xe2\\x80\\x99s business. Blockers are those tickets that are critical to customer adoption or operations.", + "title": "Support best practices | Computer for Support Teams | DevRev" + }, { "id": "ART-1986_KNOWLEDGE_NODE-38", - "text": "ticket is moved to the Closed state | The ticket was moved to Awaiting Customer Response state | The ticket moves to any state except Closed |\\n\\n**Conversations**\\n\\n| Metric | Default conditions | Start event | End event | Pause event | Resume event |\\n| --- | --- | --- | --- | --- | --- |\\n| First response time | The first message sent by a customer | Conversation created | * The agent replied to the conversation * The conversation is moved to Waiting on User/Resolved * The conversation is", + "text": "ticket is moved to the Closed state | The ticket was moved to Awaiting Customer Response state | The ticket moves to any state except Closed |\\n\\n**Conversations**\\n\\n| Metric | Default conditions | Start event | End event | Pause event | Resume event |\\n| --- | --- | --- | --- | --- | --- |\\n| First response time | The first message sent by a customer | Conversation created | * The agent replied to the conversation * The conversation is moved to Waiting on User/Resolved * The conversation is", "title": "Service-level agreement | Computer for Support Teams | DevRev" }, + { + "id": "ART-17231_KNOWLEDGE_NODE-155", + "text": "|\\n\\n**severity**\\n\\n| Value | Name | Description |\\n| --- | --- | --- |\\n| `blocker` | Blocker | - |\\n| `high` | High | - |\\n| `low` | Low | - |\\n| `medium` | Medium | - |\\n\\n**stage**\\n\\n| Value | Name | Description |\\n| --- | --- | --- |\\n| `awaiting_customer_response` | Awaiting Customer Response | - |\\n| `awaiting_development` | Awaiting Development | - |\\n| `awaiting_product_assist` | Awaiting Product Assist | - |\\n| `canceled` | Canceled | - |\\n| `in_development` | In Development | -", + "title": "Supported DevRev object types | DevRev | Docs" + }, { "id": "ART-1986_KNOWLEDGE_NODE-41", "text": "resolution is due in one day, the vista displays five minutes. In the case where the first response isn't provided within five minutes, the timer displays negative values (such as -10m), which indicates that it's been 10 minutes since the first response was due. Conversations or tickets can also be grouped by SLA stages.\\n\\nIn the **Detailed View**, all metrics applied to the ticket or conversation can be viewed along with their current stage.\\n\\nFiltering tickets by Next SLA", "title": "Service-level agreement | Computer for Support Teams | DevRev" }, { - "id": "ART-1981_KNOWLEDGE_NODE-27", - "text": "Periodically group the **Inbox** by stage and make sure there conversations only in *hold* or *awaiting customer response* stages.\\n* Let the customer know when a ticket linked to a conversation is closed and request their verification.\\n* Once all tickets of a conversation are resolved and the customer is satisfied, resolve the conversation.\\n* Move new tickets to the *awaiting product assist* stage.\\n\\nRespond to conversations\\n------------------------\\n\\n* Respond as fast as possible to any", - "title": "Support best practices | Computer for Support Teams | DevRev" + "id": "ART-1457_KNOWLEDGE_NODE-9", + "text": "\"stage\": \"foo\", \\n 83| \"status\": \"foo\" \\n 84| } \\n 85| }\\n[/code] \\n \\n[Get SLA Tracker (POST)Up Next](/public/api-reference/slas/sla-trackers-get-post)\\n\\n[Built with](https://buildwithfern.com/?utm_campaign=buildWith&utm_medium=docs&utm_source=developer.devrev.ai)\\n\\n[Enterprise grade security to protect customer dataLearn more about it.](https://devrev.ai/blog/soc-compliance)\\n\\nProduct\\n\\n * [Build](https://devrev.ai/build)\\n * [Support](https://devrev.ai/support)\\n *", + "title": "Get SLA Tracker \u2014 DevRev | Docs" }, { - "id": "ART-1986_KNOWLEDGE_NODE-39", - "text": "marked as spam | | |\\n| Next response time | | A new message on the conversation with the customer after the customer experience engineer replied | * The agent replied to the conversation * The conversation is moved to Waiting on User/Resolved * The conversation is marked as spam | | |\\n| Full resolution time | | Conversation created | * The conversation has moved to the Resolved/Archived * The conversation is marked as spam | The conversation is moved to Waiting on User | The", - "title": "Service-level agreement | Computer for Support Teams | DevRev" + "id": "ART-1827_KNOWLEDGE_NODE-469", + "text": "SLA stages.\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\nFilters for tickets with any of the provided source channels.\\nticket.subtype string Optional\\nFilters for tickets with any of the provided subtypes.\\ntype enum Optional\\nFilters for work of the provided types.\\nAllowed values: issue opportunity task ticket\\nResponse.\\n\\nThis endpoint returns an object.\\nworks list of objects\\nThe list of works.\\nShow 4 variants\\nnext_cursor string", + "title": "Update \u2014 DevRev | Docs" }, { - "id": "ART-1979_KNOWLEDGE_NODE-44", - "text": "progress* as the customer experience engineer continues to work on it.\\n* *Awaiting product assist* (APA)\\n\\n The customer experience engineer is waiting for a response or feedback from someone internally. They may need to escalate the ticket. There may be a corresponding [issue](./issues) created to fix the defect, which would transition the stage to *awaiting development*.\\n* Awaiting customer response (ACR)\\n\\n The customer experience engineer requires more detail or another response from", - "title": "Tickets | Computer for Support Teams | DevRev" + "id": "ART-1593_KNOWLEDGE_NODE-466", + "text": "SLA stages.\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\nFilters for tickets with any of the provided source channels.\\nticket.subtype string Optional\\nFilters for tickets with any of the provided subtypes.\\ntype enum Optional\\nFilters for work of the provided types.\\nAllowed values: issue opportunity task ticket\\nResponse.\\n\\nThis endpoint returns an object.\\nworks list of objects\\nThe list of works.\\nShow 4 variants\\nnext_cursor string", + "title": "Get \u2014 DevRev | Docs" } ] }, @@ -787,55 +787,55 @@ "query_id": "3cb75fc1-7ba2-447f-be4a-5bc6c5a58198", "query": "workflow send message on Slack operation execution failed Something went wrong", "retrievals": [ + { + "id": "ART-2035_KNOWLEDGE_NODE-51", + "text": "Slack.\\n\\nFor example:\\n\\n* /devrev view TKT-#\\n* /devrev view ISS-#\\n\\nThese commands open the specific object mentioned in the command.\\n\\nCreating custom workflows\\n-------------------------\\n\\nThe users can configure their own workflows around Slack using DevRev's workflow engine.\\n\\n| Workflow Action | Description | Inputs | Outputs |\\n| --- | --- | --- | --- |\\n| Send message on Slack | - Use this workflow node to send a message to any Slack channel as long as the DevRev app has access to", + "title": "Slack | Integrate | Snap-ins | DevRev" + }, { "id": "ART-10697_KNOWLEDGE_NODE-28", "text": "'Send Slack Message' workflow node to include a DevRev object.\\n* Dependent field support in slack\\n\\n![]()\\xc2\\xa0For more information about *Channels*, refer to the following articles: \\xe2\\x80\\xa3 [WhatsApp | Integrate | Snap-ins](/docs/integrations/whatsapp) \\xe2\\x80\\xa3 [Slack | Integrate | Snap-ins](/docs/integrations/slack) \\xe2\\x80\\xa3 [SLA status change Slack notifier | Automate | Snap-ins](/docs/automations/sla-change-notifier)\\n\\n![]()\\n\\n### Slack App\\n\\nMulti-region Slack support", "title": "February 2025 | Changelog | DevRev" }, { - "id": "ART-2017_KNOWLEDGE_NODE-12", - "text": "sync](/docs/automations/org-tags-sync)\\n - [Search Node](/docs/automations/search-node)\\n - [Sentiment evaluator](/docs/automations/sentiment-evaluator)\\n - [Subtype Migration](/docs/automations/subtype-migration)\\n - [Real-time sentiment evaluator](/docs/automations/realtime-sentiment-evaluator)\\n - [Send customized emails](/docs/automations/send-emails)\\n - [StageFlow automator](/docs/automations/stageflow-automator)\\n - [Smart issue", - "title": "SLA status change Slack notifier | Automate | Snap-ins | DevRev" - }, - { - "id": "ART-2017_KNOWLEDGE_NODE-16", - "text": "sync](/docs/automations/ticket-linked-issues-comment-sync)\\n - [Slack message agent](/docs/automations/slack-message-agent)\\n + [Integrate](/docs/integrate)\\n\\n - [Bitbucket](/docs/integrations/bitbucket)\\n - [Calendly](/docs/integrations/calendly)\\n - [Coralogix security integration](/docs/integrations/coralogix)\\n - [Datadog](/docs/integrations/datadog)\\n - [Google Calendar AirSync](/docs/integrations/google-calendar-airdrop)\\n - [Email](/docs/integrations/email)\\n\\n", - "title": "SLA status change Slack notifier | Automate | Snap-ins | DevRev" + "id": "ART-12394_KNOWLEDGE_NODE-31", + "text": "workflow.\\n* **Define error actions**: Set a specific sequence of steps to execute if an error occurs during that action.\\n* **Ensure graceful management**: Manage errors by enabling appropriate fallback actions, such as sending a notification or logging the error. When a step fails, any subsequent steps in the path do not execute.\\n\\n[PreviousConversational workflows](/docs/product/conversational-workflows)[NextWorkflow nodes](/docs/product/workflow-nodes)\\n\\n#### On this page\\n\\n* [Version", + "title": "Workflow management | Workflows | Computer by DevRev | DevRev" }, { - "id": "ART-2035_KNOWLEDGE_NODE-48", - "text": "channel.\\n\\n1. **Sync messages with the thread (for incidents created from Slack)**\\n\\n* Works only for incidents created from Slack.\\n* It syncs messages with the originating thread, similar to ticket and issue work items.\\n\\n1. **Sync messages with the notification thread**\\n\\n* Syncs with the thread of the incident notification sent on the channel mentioned in the **Channel ID to send incident notifications** configuration.\\n* Works for all incidents irrespective of source channel or", - "title": "Slack | Integrate | Snap-ins | DevRev" + "id": "ART-4206_KNOWLEDGE_NODE-3", + "text": "it.\\n* Complete execution tracking via progress events.\\n* Ability to handle long-running agent tasks.\\n\\n##### \\n\\nIn any unlikely and unforeseen circumstances, if an individual operation of the workflow times out, you do not receive an error event right now to notify that you should not wait for any more messages. It is better to have a client side timeout for now while the issue is brainstormed and fixed for you.\\n\\nSet up webhook\\n--------------\\n\\nBefore using the async API, you need to", + "title": "Agents async API | DevRev | Docs" }, { - "id": "ART-4199_KNOWLEDGE_NODE-13", - "text": "group](/docs/automations/set-user-preference)\\n - [SLA status change Slack notifier](/docs/automations/sla-change-notifier)\\n - [Slash commands](/docs/automations/slash-commands)\\n - [Spam Shield](/docs/automations/spam-shield)\\n - [Subtype Migration](/docs/automations/subtype-migration)\\n - [Ticket age in engineering](/docs/automations/ticket-age-in-engineering)\\n - [Ticket issue field migrator](/docs/automations/ticket-issue-field-migrator)\\n - [Ticket", - "title": "Slack message agent | Automate | Snap-ins | DevRev" + "id": "ART-2004_KNOWLEDGE_NODE-29", + "text": "approval workflow](/docs/automations/ticket-approval-workflow) | | |\\n| [Slack message agent](/docs/automations/slack-message-agent) | | |\\n| [Tracxn sync](/docs/automations/tracxn-sync) | | |\\n| [Airtable](/docs/automations/airtable) | | |\\n\\nBuild\\n-----\\n\\n| Automate | Integrate | AirSync |\\n| --- | --- | --- |\\n| [Convergence](/docs/automations/converge) | [GitHub](/docs/integrations/github) | [Jira](/docs/integrations/jira) |\\n| [Work duration](/docs/automations/work-duration) |", + "title": "Snap-ins | DevRev" }, { - "id": "ART-4199_KNOWLEDGE_NODE-10", - "text": "data](/docs/automations/bulk-delete)\\n - [Bulk work item uploader](/docs/automations/bulk-upload)\\n - [Commands surface expander](/docs/automations/commands-surface-expander)\\n - [Convergence](/docs/automations/converge)\\n - [Conversation reminder](/docs/automations/conversation-reminder)\\n - [CSAT on conversation](/docs/automations/csat-conv)\\n - [CSAT on ticket](/docs/automations/csat-tickets)\\n - [CSV work item uploader](/docs/automations/csv-work-item-uploader)\\n -", - "title": "Slack message agent | Automate | Snap-ins | DevRev" + "id": "ART-2035_KNOWLEDGE_NODE-54", + "text": "given DevRev user - Can be used to later send direct messages to the user on the Slack using Send message to Slack node. | - Slack connection - DevRev user id | - Slack user id |\\n| Start Thread Sync | - Set up 2 way message synchronization between a Slack thread and a DevRev object discussion. | - Slack connection - DevRev Object ID - Slack channel ID - Slack thread ID (message ID of parent message, returned by send message to Slack workflow node) | N/A |\\n| Start Channel Sync | -", + "title": "Slack | Integrate | Snap-ins | DevRev" }, { - "id": "ART-4199_KNOWLEDGE_NODE-28", - "text": "**Trigger URL** that is displayed.\\n6. Paste the Trigger URL under **Enable Events** in the custom Slack bot.\\n\\n[PreviousTicket linked issues comment sync](/docs/automations/ticket-linked-issues-comment-sync)[NextIntegrate](/docs/integrate)\\n\\n#### On this page\\n\\n* [Install](#install)\\n* [Configure the custom Slack bot](#configure-the-custom-slack-bot)\\n* [Configure DevRev](#configure-devrev)\\n\\n[Enterprise grade security to protect customer data\\n\\nLearn more about", - "title": "Slack message agent | Automate | Snap-ins | DevRev" + "id": "ART-2035_KNOWLEDGE_NODE-45", + "text": "Creating issues with sync enabled from external channels is not supported.\\n\\nDevRev Incidents and Slack\\n--------------------------\\n\\n![]()\\n\\nIncident Management is available as a **beta feature**. Contact the support team to enable it before configuring incident settings.\\n\\nThe Slack snap-in allows incident creation directly from Slack using the following methods:\\n\\n* Use the /devrev create-incident command.\\n* Select **Create a new incident** from the message actions.\\n* Enable", + "title": "Slack | Integrate | Snap-ins | DevRev" }, { - "id": "ART-4199_KNOWLEDGE_NODE-17", - "text": "[Slack](/docs/integrations/slack)\\n - [WhatsApp](/docs/integrations/whatsapp)\\n - [GitHub](/docs/integrations/github)\\n - [GitLab](/docs/integrations/gitlab)\\n - [Harness](/docs/integrations/harness)\\n - [Marker.io](/docs/integrations/marker-io)\\n - [Instabug](/docs/integrations/instabug)\\n - [Qase](/docs/integrations/qase)\\n - [Tracxn Integration](/docs/integrations/tracxn-integration)\\n - [Twilio](/docs/integrations/twilio)\\n - [Glean](/docs/integrations/glean)\\n", - "title": "Slack message agent | Automate | Snap-ins | DevRev" + "id": "ART-4206_KNOWLEDGE_NODE-20", + "text": "occurred |\\n| 49 | sendToClient(conversationId, { |\\n| 50 | type: \"agent_error\", |\\n| 51 | error: event.payload.ai_agent_response.error.error, |\\n| 52 | }); |\\n| 53 | } |\\n| 54 | |\\n| 55 | res.status(200).send(\"OK\"); |\\n| 56 | }); |\\n```\\n\\n##### \\n\\nUsing WebSockets or Server-Sent Events can provide real-time updates to your\\nUI as events are received.\\n\\n### Talk to agent node in workflows\\n\\n##### \\n\\nThis is in early access, please contact support to have it enabled for you.\\n\\nIf", + "title": "Agents async API | DevRev | Docs" }, { - "id": "ART-2017_KNOWLEDGE_NODE-25", - "text": "ticket\\'s owner and subscribers, when a ticket\\'s resolution time SLA changes into the *Warning* or *Breached* stage.\\n\\n![]()\\n\\nFor more information, refer to the\\n[SLA status change Slack notifier snap-in](/marketplace/sla-status-change-slack-notifier) on the DevRev\\nmarketplace.\\n\\nInstallation\\n------------\\n\\n1. Create a Slack app for your workspace in .\\n2. In App features, generate bot token in **OAuth & Permissions**.\\n3. Grant the app bot the following", - "title": "SLA status change Slack notifier | Automate | Snap-ins | DevRev" + "id": "ART-2035_KNOWLEDGE_NODE-52", + "text": "the channel. - Private channels are supported only if the DevRev app is a member of the channel. | - Slack connection - Slack channel id - Text message to send - Objects to mention with message - If any object is added here, a summary card of that object is sent with the message. | Slack message ID |\\n| Create new Slack channel | Use this workflow node to create a new Slack channel. | - Slack connection - Channel name Make sure this is unique. It is recommended to create this name", + "title": "Slack | Integrate | Snap-ins | DevRev" }, { - "id": "ART-4199_KNOWLEDGE_NODE-27", - "text": "message.channels.\\n7. Add this custom app and the **DevRev Slack Bot** into the Slack channel from which you want to create the DevRev object.\\n\\nConfigure DevRev\\n----------------\\n\\n1. Add the Slack Signing Secret and Slack Bot Token copied from the custom Slack bot app.\\n2. Add the channel IDs for either incidents, tickets or issues.\\n3. Click the respective buttons to enable the sync between threads.\\n4. Select the part ID to associate a particular part.\\n5. Click **Save** and copy the", - "title": "Slack message agent | Automate | Snap-ins | DevRev" + "id": "ART-8442_KNOWLEDGE_NODE-15", + "text": "uploader](/docs/automations/csv-work-item-uploader)\\n * [CSV comments uploader](/docs/automations/csv-comments-uploader)\\n * [Ticket approval workflow](/docs/automations/ticket-approval-workflow)\\n * [Ticket linked issues comment sync](/docs/automations/ticket-linked-issues-comment-sync)\\n * [Slack message agent](/docs/automations/slack-message-agent)\\n\\n * [Integrate](/docs/integrate)\\n\\n * [Bitbucket](/docs/integrations/bitbucket)\\n *", + "title": "January 2025 | Changelog | DevRev" } ] }, @@ -844,54 +844,54 @@ "query": "change and customize chat design", "retrievals": [ { - "id": "ART-12974_KNOWLEDGE_NODE-2", - "text": "{ \\n ---|--- \\n 2| \"chat\": { \\n 3| \"type\": \"foo\" \\n 4| } \\n 5| }\\n[/code] \\n \\n[Create Code ChangeUp Next](/public/api-reference/code-changes/create)\\n\\n[Built with](https://buildwithfern.com/?utm_campaign=buildWith&utm_medium=docs&utm_source=developer.devrev.ai)\\n\\n[Enterprise grade security to protect customer dataLearn more about it.](https://devrev.ai/blog/soc-compliance)\\n\\nProduct\\n\\n * [Build](https://devrev.ai/build)\\n *", - "title": "Update Chat \u2014 DevRev | Docs" + "id": "ART-2898_KNOWLEDGE_NODE-15", + "text": "to tailor its appearance to your application\\xe2\\x80\\x99s design.\\n\\n[code]\\n\\n 1| android:src=\"@your_drawable_here\" \\n ---|---\\n[/code] \\n \\nand\\n\\n[code]\\n\\n 1| android:backgroundTint=\"@your_background_color\" \\n ---|---\\n[/code] \\n \\nAt this stage, your app is fully configured to utilize all functionalities of the DevRev PLuG SDK. Pressing the support button directs the user to the chat interface, enabling effective interaction and support.\\n\\n## Analytics\\n\\nThe DevRev SDK", + "title": "Android integration \u2014 DevRev | Docs" }, { - "id": "ART-15306_KNOWLEDGE_NODE-3", - "text": "Change\\n\\nNext](/api-reference/code-changes/create)[Built with](https://buildwithfern.com/?utm_campaign=buildWith&utm_medium=docs&utm_source=developer.devrev.ai)'", - "title": "Update Chat | DevRev | Docs" + "id": "ART-3109_KNOWLEDGE_NODE-25", + "text": "Plug widget to reflect your unique identity truly.\\n\\nTo configure the appearance of your Plug widget, open your DevRev app and navigate to **Settings > Support > Plug Chat > Configuration, Styling, and Layout**.\\n\\n### Configuration\\n\\n* Hide Plug widget: Hide the Plug Widget on specific URLs by clicking **+ Rule** and adding the URLs you want to configure.\\n\\n### Styling\\n\\n* Launcher logo: The image that's visible as your widget icon. A 20-pixel square image is recommended.\\n* Alignment: The", + "title": "Plug widget customization | Computer for Your Customers | DevRev" }, { - "id": "ART-2059_KNOWLEDGE_NODE-5", - "text": "Jul 06 to Jul 19, 2023 Jun 20 to Jul 05, 2023 Jun 05 to Jun 19, 2023 May 22 to Jun 05, 2023 Apr 22 to May 22, 2023\\n\\nDeveloper DevRevU\\n\\nOn this page\\nIntegration code Unique app ID Setup for HTML Setup for React\\nInstall PLuG chat on your website.\\n\\nThere are two primary methods to customize PLuG chat. The easiest way is to do so through the app by navigating to Settings > Support > PLuG Settings > Configuration, Styling and Layout Tabs.. For detailed descriptions of the parameters, refer", - "title": "Install PLuG chat on your website" + "id": "ART-4230_KNOWLEDGE_NODE-1", + "text": "https://api.devrev.ai/chats.create \\\\ \\n ---|--- \\n >| -H \"Authorization: Bearer \" \\\\ \\n >| -H \"Content-Type: application/json\" \\\\ \\n >| -d \\'{ \\n >| \"type\": \"dm\", \\n >| \"users\": [ \\n >| \"users\", \\n >| \"users\" \\n >| ] \\n >| }\\'\\n[/code] \\n \\nTry it\\n\\n201Created\\n\\n[code]\\n\\n 1| { \\n ---|--- \\n 2| \"chat\": { \\n 3| \"type\": \"dm\", \\n 4| \"id\": \"id\", \\n 5| \"users\": [ \\n 6| {", + "title": "Create Chat (Beta) \u2014 DevRev | Docs" }, { - "id": "ART-15306_KNOWLEDGE_NODE-0", - "text": "b'Update Chat | DevRev | Docs\\n\\n[![]()![]()](https://developer.devrev.ai/)\\n\\nPublic\\n\\nPublic\\n\\nSearch\\n\\n`/`\\n\\n[API Reference](/api-reference/getting-started)[chats](/api-reference/chats/create)\\n\\nUpdate Chat\\n===========\\n\\nCopy page\\n\\nPOST\\n\\nhttps://api.devrev.ai/chats.update\\n\\nPOST\\n\\n/chats.update\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl -X POST https://api.devrev.ai/chats.update \\\\ |\\n| > | -H \"Authorization: Bearer \" \\\\ |\\n| > | -H \"Content-Type: application/json\" \\\\ |\\n|", - "title": "Update Chat | DevRev | Docs" + "id": "ART-2059_KNOWLEDGE_NODE-6", + "text": "to the Customize documentation.\\n\\nAlternatively, for the most comprehensive customizations, refer to our SDK functions here.\\n\\nIntegration code.\\n\\nTo get the PLuG chat widget to appear on your website and web app, copy and paste the snippet below on every page where you want the widget to appear for website visitors.\\n\\nUnique app ID.\\n\\nMake sure to replace the app ID with your app ID which identifies your PLuG chat widget. You can access your app ID from your DevRev account by following", + "title": "Install PLuG chat on your website" }, { - "id": "ART-12971_KNOWLEDGE_NODE-3", - "text": ">| ] \\n >| }\\'\\n[/code] \\n \\nTry it\\n\\n201chatsCreateExample\\n\\n[code]\\n\\n 1| { \\n ---|--- \\n 2| \"chat\": { \\n 3| \"type\": \"foo\" \\n 4| } \\n 5| }\\n[/code] \\n \\n[Get ChatUp Next](/public/api-reference/chats/get)\\n\\n[Built with](https://buildwithfern.com/?utm_campaign=buildWith&utm_medium=docs&utm_source=developer.devrev.ai)\\n\\n[Enterprise grade security to protect customer dataLearn more about it.](https://devrev.ai/blog/soc-compliance)\\n\\nProduct\\n\\n *", - "title": "Create Chat \u2014 DevRev | Docs" + "id": "ART-4115_KNOWLEDGE_NODE-10", + "text": "], \\n 95| \"surface\": \"customer_chat\" \\n 96| } \\n 97| ], \\n 98| \"usage_hint\": \"usage_hint\" \\n 99| } \\n 100| }\\n[/code] \\n \\n[Create Content TemplateUp Next](/beta/api-reference/notifications/content-template-create)\\n\\n[Built with](https://buildwithfern.com/?utm_campaign=buildWith&utm_medium=docs&utm_source=developer.devrev.ai)\\n\\n'", + "title": "Update Command (Beta) \u2014 DevRev | Docs" }, { - "id": "ART-12974_KNOWLEDGE_NODE-9", - "text": "demo](https://devrev.ai/request-a-demo)\\n\\n'", - "title": "Update Chat \u2014 DevRev | Docs" + "id": "ART-3231_KNOWLEDGE_NODE-25", + "text": "**Configure**.\\n2. Fill in the configuration settings.\\n\\n * **Command Names**: List command names that exist in the organization. Enter\\n one per text box (to add more text boxes, click \\'**+**\\').\\n * **Customer Chat Surfaces**: Select surfaces where the commands should be\\n available in the \"Customer messages\".\\n * **Discussions Surfaces**: Select surfaces where the commands should be\\n available in internal chats.\\n3. Click **Save**.\\n4. Click **Install** to activate the", + "title": "Commands surface expander | Automate | Snap-ins | DevRev" }, { - "id": "ART-15301_KNOWLEDGE_NODE-3", - "text": "with](https://buildwithfern.com/?utm_campaign=buildWith&utm_medium=docs&utm_source=developer.devrev.ai)'", - "title": "Create Chat | DevRev | Docs" + "id": "ART-15311_KNOWLEDGE_NODE-5", + "text": "\"account\" |\\n| 75 | ], |\\n| 76 | \"surface\": \"customer_chat\" |\\n| 77 | } |\\n| 78 | ], |\\n| 79 | \"usage_hint\": \"string\" |\\n| 80 | } |\\n| 81 | } |\\n```\\n\\nGets a command.\\n\\n### Headers\\n\\nAuthorizationstringRequired\\n\\nBearer authentication of the form `Bearer `, where token is your auth token.\\n\\n### Query parameters\\n\\nidstringRequired`format: \"id\"`\\n\\nThe command\\'s ID.\\n\\n### Response\\n\\nSuccess.\\n\\ncommandobject\\n\\nShow 14 properties\\n\\n### Errors\\n\\n400\\n\\nBad Request", + "title": "Get Command | DevRev | Docs" }, { - "id": "ART-3109_KNOWLEDGE_NODE-29", - "text": "go to **Settings > Support > Plug Chat > Layout** through the settings icon on the top-left corner.\\n2. Select **Add a Card** and enter a title, description, image, and redirect URL.\\n3. Click **Save and Publish** in the top-right corner. The new card is visible in your Plug widget.\\n\\nWant to add more personalization to your Plug widget? Create your own. Visit [SDK Methods and Customization](https://developer.devrev.ai/sdks/web/customize) to create your own Plug from the ground", - "title": "Plug widget customization | Computer for Your Customers | DevRev" + "id": "ART-15312_KNOWLEDGE_NODE-5", + "text": "|\\n| 75 | \"account\" |\\n| 76 | ], |\\n| 77 | \"surface\": \"customer_chat\" |\\n| 78 | } |\\n| 79 | ], |\\n| 80 | \"usage_hint\": \"string\" |\\n| 81 | } |\\n| 82 | ], |\\n| 83 | \"next_cursor\": \"string\", |\\n| 84 | \"prev_cursor\": \"string\" |\\n| 85 | } |\\n```\\n\\nLists commands for a Dev organization.\\n\\n### Headers\\n\\nAuthorizationstringRequired\\n\\nBearer authentication of the form `Bearer `, where token is your auth token.\\n\\n### Query parameters\\n\\ncursorstringOptional`format: \"text\"`\\n\\nThe cursor to", + "title": "List Commands | DevRev | Docs" }, { - "id": "ART-2897_KNOWLEDGE_NODE-7", - "text": "button text for new tickets and conversations, conversation user text, and more. It must be a valid hex color code, such as `#f0f0f0`.| String \\n`session_recording_options`| Options for recording observability sessions.| Refer to [Session recording options](https://devrev.ai/docs/plug/session-recording) \\n`accent_color`| The accent color of the PLuG affects the launcher, new ticket and conversation buttons, conversation user text, and more.| String \\n`custom_launcher_selector`| A CSS", - "title": "Methods \u2014 DevRev | Docs" + "id": "ART-12986_KNOWLEDGE_NODE-11", + "text": "\\n 71| \"account\" \\n 72| ], \\n 73| \"surface\": \"customer_chat\" \\n 74| } \\n 75| ], \\n 76| \"usage_hint\": \"foo\" \\n 77| } \\n 78| ], \\n 79| \"next_cursor\": \"foo\", \\n 80| \"prev_cursor\": \"foo\" \\n 81| }\\n[/code] \\n \\n[Update CommandUp Next](/public/api-reference/commands/update)\\n\\n[Built", + "title": "List Commands (POST) \u2014 DevRev | Docs" }, { - "id": "ART-12971_KNOWLEDGE_NODE-9", - "text": "Status](https://devrev.ai/status)\\n\\n\\xc2\\xa9 2025 DevRev Inc.\\n\\n'", - "title": "Create Chat \u2014 DevRev | Docs" + "id": "ART-4110_KNOWLEDGE_NODE-10", + "text": "], \\n 95| \"surface\": \"customer_chat\" \\n 96| } \\n 97| ], \\n 98| \"usage_hint\": \"usage_hint\" \\n 99| } \\n 100| }\\n[/code] \\n \\n[Get CommandUp Next](/beta/api-reference/commands/get)\\n\\n[Built with](https://buildwithfern.com/?utm_campaign=buildWith&utm_medium=docs&utm_source=developer.devrev.ai)\\n\\n'", + "title": "Create Command (Beta) \u2014 DevRev | Docs" } ] }, @@ -900,54 +900,54 @@ "query": "Vista export as CSV error invalid_field sort_groups_by", "retrievals": [ { - "id": "ART-1949_KNOWLEDGE_NODE-27", - "text": "bar.\\n\\n![]()\\n\\nTo export vistas to CSV or JSON, click **Actions** and select the format in which you want to export the vista. This allows you to export this data with the filters applied (segmented by owners or some filters). Cross-functional teams can collaborate on this data or import it into other platforms.\\n\\nDelete a vista\\n--------------\\n\\n1. Select the vista you want to delete from **My list** and click the edit button next to the name of your vista.\\n2. Click **Remove access**.\\n3.", - "title": "Vistas | Computer by DevRev | DevRev" + "id": "ART-2065_KNOWLEDGE_NODE-30", + "text": "items into visual cards, organized in columns and rows. It enhances workflow visualization, limits work in progress, and allows drag-and-drop management through different stages. Ideal for moving tickets, tracking issues, and managing sales opportunities.\\n* When exporting a view as CSV, you can now choose to export either all columns of the record or only the columns currently displayed in your view.\\n* In list views, when grouping issues or tickets, you can now sort group labels by their", + "title": "August 2025 | Changelog | DevRev" }, { - "id": "ART-15481_KNOWLEDGE_NODE-6", - "text": "not set, then no later elements exist.\\n\\nprev\\\\_cursorstring or null`format: \"text\"`\\n\\nThe cursor used to iterate preceding results in accordance to the\\nsort order. If not set, then no prior elements exist.\\n\\nvista\\\\_grouplist of objects or null\\n\\nList of vista group items.\\n\\nShow 3 variants\\n\\n### Errors\\n\\n400\\n\\nBad Request Error\\n\\n401\\n\\nUnauthorized Error\\n\\n403\\n\\nForbidden Error\\n\\n429\\n\\nToo Many Requests Error\\n\\n500\\n\\nInternal Server Error\\n\\n503\\n\\nService Unavailable", - "title": "List Vistas Groups | DevRev | Docs" + "id": "ART-15483_KNOWLEDGE_NODE-10", + "text": "\"text\"`\\n\\nThe cursor used to iterate preceding results in accordance to the\\nsort order. If not set, then no prior elements exist.\\n\\n### Errors\\n\\n400\\n\\nBad Request Error\\n\\n401\\n\\nUnauthorized Error\\n\\n403\\n\\nForbidden Error\\n\\n429\\n\\nToo Many Requests Error\\n\\n500\\n\\nInternal Server Error\\n\\n503\\n\\nService Unavailable Error\\n\\nWas this page helpful?\\n\\nYesNo\\n\\n[Previous](/api-reference/vistas/groups-list-post)[#### List Vistas (POST)\\n\\nNext](/api-reference/vistas/list-post)[Built", + "title": "List Vistas | DevRev | Docs" }, { - "id": "ART-1302_KNOWLEDGE_NODE-161", - "text": "will always be returned in the specified sort-by order.\\nsort_by list of strings Optional\\nComma-separated fields to sort the groups by.\\nResponse.\\n\\nThis endpoint returns an object.\\ngroups list of objects\\nThe list of groups.\\nShow 11 properties\\nnext_cursor string Optional\\nThe cursor used to iterate subsequent results in accordance to the sort order. If not set, then no later elements exist.\\nprev_cursor string Optional\\nThe cursor used to iterate preceding results in accordance to the", - "title": "Export \u2014 DevRev | Docs" + "id": "ART-15465_KNOWLEDGE_NODE-6", + "text": "values:afterbefore\\n\\nmodified\\\\_dateobjectOptional\\n\\nProvides ways to specify date ranges on objects.\\n\\nShow 2 variants\\n\\nparent\\\\_idlist of stringsOptional\\n\\nParent ID of the vista group item.\\n\\nsort\\\\_bylist of stringsOptional\\n\\nComma-separated fields to sort the objects by.\\n\\nstart\\\\_dateobjectOptional\\n\\nProvides ways to specify date ranges on objects.\\n\\nShow 2 variants\\n\\nstatelist of enumsOptional\\n\\nDenotes the state of the vista group item.\\n\\nAllowed", + "title": "List Vistas Groups (POST) | DevRev | Docs" }, { - "id": "ART-15481_KNOWLEDGE_NODE-5", - "text": "stringsOptional\\n\\nComma-separated fields to sort the objects by.\\n\\nstatelist of enumsOptional\\n\\nDenotes the state of the vista group item.\\n\\nAllowed values:activecompletedplanned\\n\\ntypelist of enumsOptional\\n\\nFilters for vista group items of the specific type.\\n\\nAllowed values:curateddynamic\\n\\n### Response\\n\\nThe response to listing the vistas group items.\\n\\nnext\\\\_cursorstring or null`format: \"text\"`\\n\\nThe cursor used to iterate subsequent results in accordance to the\\nsort order. If", - "title": "List Vistas Groups | DevRev | Docs" + "id": "ART-15465_KNOWLEDGE_NODE-5", + "text": "information about a list of vista groups.\\n\\nmodeenumOptional\\n\\nThe iteration mode to use. If \\xe2\\x80\\x9cafter\\xe2\\x80\\x9d, then entries after the provided\\ncursor will be returned, or if no cursor is provided, then from the\\nbeginning. If \\xe2\\x80\\x9cbefore\\xe2\\x80\\x9d, then entries before the provided cursor will be\\nreturned, or if no cursor is provided, then from the end. Entries will\\nalways be returned in the specified sort-by order.\\n\\nAllowed", + "title": "List Vistas Groups (POST) | DevRev | Docs" }, { - "id": "ART-15481_KNOWLEDGE_NODE-1", - "text": "it](/api-reference/vistas/groups-list?explorer=true)\\n\\n200Retrieved\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | { |\\n| 2 | \"next_cursor\": \"string\", |\\n| 3 | \"prev_cursor\": \"string\", |\\n| 4 | \"vista_group\": [ |\\n| 5 | { |\\n| 6 | \"end_date\": \"2023-01-01T12:00:00.000Z\", |\\n| 7 | \"id\": \"string\", |\\n| 8 | \"name\": \"string\", |\\n| 9 | \"parent\": { |\\n| 10 | \"type\": \"string\", |\\n| 11 | \"display_id\": \"string\", |\\n| 12 | \"flavor\": \"nnl\", |\\n| 13 | \"id\": \"VISTA-12345\", |\\n| 14 | \"name\": \"string\" |\\n| 15 | },", + "id": "ART-15481_KNOWLEDGE_NODE-5", + "text": "stringsOptional\\n\\nComma-separated fields to sort the objects by.\\n\\nstatelist of enumsOptional\\n\\nDenotes the state of the vista group item.\\n\\nAllowed values:activecompletedplanned\\n\\ntypelist of enumsOptional\\n\\nFilters for vista group items of the specific type.\\n\\nAllowed values:curateddynamic\\n\\n### Response\\n\\nThe response to listing the vistas group items.\\n\\nnext\\\\_cursorstring or null`format: \"text\"`\\n\\nThe cursor used to iterate subsequent results in accordance to the\\nsort order. If", "title": "List Vistas Groups | DevRev | Docs" }, { - "id": "ART-15479_KNOWLEDGE_NODE-1", - "text": "|\\n```\\n\\n[Try it](/api-reference/vistas/groups-get?explorer=true)\\n\\n200Retrieved\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | { |\\n| 2 | \"vista_group\": { |\\n| 3 | \"end_date\": \"2023-01-01T12:00:00.000Z\", |\\n| 4 | \"id\": \"string\", |\\n| 5 | \"name\": \"string\", |\\n| 6 | \"parent\": { |\\n| 7 | \"type\": \"string\", |\\n| 8 | \"display_id\": \"string\", |\\n| 9 | \"flavor\": \"nnl\", |\\n| 10 | \"id\": \"VISTA-12345\", |\\n| 11 | \"name\": \"string\" |\\n| 12 | }, |\\n| 13 | \"start_date\": \"2023-01-01T12:00:00.000Z\", |\\n| 14 | \"state\":", - "title": "Get Vistas Group | DevRev | Docs" + "id": "ART-15465_KNOWLEDGE_NODE-7", + "text": "values:activecompletedplanned\\n\\n### Response\\n\\nThe response to listing the vistas group items.\\n\\nnext\\\\_cursorstring or null`format: \"text\"`\\n\\nThe cursor used to iterate subsequent results in accordance to the\\nsort order. If not set, then no later elements exist.\\n\\nprev\\\\_cursorstring or null`format: \"text\"`\\n\\nThe cursor used to iterate preceding results in accordance to the\\nsort order. If not set, then no prior elements exist.\\n\\nvista\\\\_grouplist of objects or null\\n\\nList of vista", + "title": "List Vistas Groups (POST) | DevRev | Docs" }, { - "id": "ART-15463_KNOWLEDGE_NODE-1", - "text": "|\\n| > | -H \"Content-Type: application/json\" \\\\ |\\n| > | -d \\'{ |\\n| > | \"id\": \"string\" |\\n| > | }\\' |\\n```\\n\\n[Try it](/api-reference/vistas/groups-get-post?explorer=true)\\n\\n200Successful\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | { |\\n| 2 | \"vista_group\": { |\\n| 3 | \"end_date\": \"2023-01-01T12:00:00.000Z\", |\\n| 4 | \"id\": \"string\", |\\n| 5 | \"name\": \"string\", |\\n| 6 | \"parent\": { |\\n| 7 | \"type\": \"string\", |\\n| 8 | \"display_id\": \"string\", |\\n| 9 | \"flavor\": \"nnl\", |\\n| 10 | \"id\": \"VISTA-12345\", |\\n|", - "title": "Get Vistas Group (POST) | DevRev | Docs" + "id": "ART-1530_KNOWLEDGE_NODE-2", + "text": "\\xe2\\x80\\x9cafter\\xe2\\x80\\x9d is used.\\n\\nAllowed values: afterbefore\\n\\nsort_bystringOptional\\n\\nComma-separated fields to sort the groups by.\\n\\n### Response\\n\\nThe response to listing the groups.\\n\\ngroupslist of objects\\n\\nThe list of groups.\\n\\nShow 12 properties\\n\\nnext_cursorstringOptional\\n\\nThe cursor used to iterate subsequent results in accordance to the sort order. If not set, then no later elements exist.\\n\\nprev_cursorstringOptional\\n\\nThe cursor used to iterate preceding results", + "title": "List Groups (Beta) \u2014 DevRev | Docs" }, { - "id": "ART-15465_KNOWLEDGE_NODE-6", - "text": "values:afterbefore\\n\\nmodified\\\\_dateobjectOptional\\n\\nProvides ways to specify date ranges on objects.\\n\\nShow 2 variants\\n\\nparent\\\\_idlist of stringsOptional\\n\\nParent ID of the vista group item.\\n\\nsort\\\\_bylist of stringsOptional\\n\\nComma-separated fields to sort the objects by.\\n\\nstart\\\\_dateobjectOptional\\n\\nProvides ways to specify date ranges on objects.\\n\\nShow 2 variants\\n\\nstatelist of enumsOptional\\n\\nDenotes the state of the vista group item.\\n\\nAllowed", - "title": "List Vistas Groups (POST) | DevRev | Docs" + "id": "ART-1801_KNOWLEDGE_NODE-156", + "text": "groups on basis of member type.\\nAllowed values: dev_user rev_user\\nmode \"after\" or \"before\" Optional\\nThe iteration mode to use, otherwise if not set, then \"after\" is used.\\nAllowed values: after before\\nsort_by string Optional\\nComma-separated fields to sort the groups by.\\nResponse.\\n\\nThis endpoint returns an object.\\ngroups list of objects\\nThe list of groups.\\nShow 11 properties\\nnext_cursor string Optional\\nThe cursor used to iterate subsequent results in accordance to the sort order. If", + "title": "Get \u2014 DevRev | Docs" }, { - "id": "ART-15465_KNOWLEDGE_NODE-5", - "text": "information about a list of vista groups.\\n\\nmodeenumOptional\\n\\nThe iteration mode to use. If \\xe2\\x80\\x9cafter\\xe2\\x80\\x9d, then entries after the provided\\ncursor will be returned, or if no cursor is provided, then from the\\nbeginning. If \\xe2\\x80\\x9cbefore\\xe2\\x80\\x9d, then entries before the provided cursor will be\\nreturned, or if no cursor is provided, then from the end. Entries will\\nalways be returned in the specified sort-by order.\\n\\nAllowed", - "title": "List Vistas Groups (POST) | DevRev | Docs" + "id": "ART-1791_KNOWLEDGE_NODE-153", + "text": "groups on basis of member type.\\nAllowed values: dev_user rev_user\\nmode \"after\" or \"before\" Optional\\nThe iteration mode to use, otherwise if not set, then \"after\" is used.\\nAllowed values: after before\\nsort_by string Optional\\nComma-separated fields to sort the groups by.\\nResponse.\\n\\nThis endpoint returns an object.\\ngroups list of objects\\nThe list of groups.\\nShow 11 properties\\nnext_cursor string Optional\\nThe cursor used to iterate subsequent results in accordance to the sort order. If", + "title": "Self Delete \u2014 DevRev | Docs" }, { - "id": "ART-15465_KNOWLEDGE_NODE-1", - "text": "\" \\\\ |\\n| > | -H \"Content-Type: application/json\" \\\\ |\\n| > | -d \\'{}\\' |\\n```\\n\\n[Try it](/api-reference/vistas/groups-list-post?explorer=true)\\n\\n200Successful\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | { |\\n| 2 | \"next_cursor\": \"string\", |\\n| 3 | \"prev_cursor\": \"string\", |\\n| 4 | \"vista_group\": [ |\\n| 5 | { |\\n| 6 | \"end_date\": \"2023-01-01T12:00:00.000Z\", |\\n| 7 | \"id\": \"string\", |\\n| 8 | \"name\": \"string\", |\\n| 9 | \"parent\": { |\\n| 10 | \"type\": \"string\", |\\n| 11 | \"display_id\": \"string\",", - "title": "List Vistas Groups (POST) | DevRev | Docs" + "id": "ART-1300_KNOWLEDGE_NODE-154", + "text": "groups on basis of member type.\\nAllowed values: dev_user rev_user\\nmode \"after\" or \"before\" Optional\\nThe iteration mode to use, otherwise if not set, then \"after\" is used.\\nAllowed values: after before\\nsort_by string Optional\\nComma-separated fields to sort the groups by.\\nResponse.\\n\\nThis endpoint returns an object.\\ngroups list of objects\\nThe list of groups.\\nShow 11 properties\\nnext_cursor string Optional\\nThe cursor used to iterate subsequent results in accordance to the sort order. If", + "title": "Create \u2014 DevRev | Docs" } ] }, @@ -956,54 +956,54 @@ "query": "accounts.export API filter by created date after", "retrievals": [ { - "id": "ART-1254_KNOWLEDGE_NODE-7", - "text": "\"date-time\"`\\n\\nFilters for objects created after the provided timestamp (inclusive).\\n\\nmodified\\\\_date.beforestringOptional`format: \"date-time\"`\\n\\nFilters for objects created before the provided timestamp\\n(inclusive).\\n\\nsort\\\\_bylist of stringsOptional\\n\\nFields to sort the accounts by and the direction to sort them in.\\n\\nstagelist of stringsOptional\\n\\nFilters for accounts on specified stages.\\n\\ntierlist of stringsOptional\\n\\nTier of the accounts to be filtered.\\n\\nwebsiteslist of", - "title": "Export Accounts | DevRev | Docs" + "id": "ART-1302_KNOWLEDGE_NODE-8", + "text": "\" : \" value \" 3 }\\nAPI Reference accounts Export.\\n\\nGET https:// api.devrev.ai / accounts.export\\nExports a collection of accounts.\\nQuery parameters.\\n\\ncreated_by string Optional\\nFilters for accounts created by the specified user(s).\\ncreated_date.after datetime Optional\\nFilters for objects created after the provided timestamp (inclusive).\\ncreated_date.before datetime Optional\\nFilters for objects created before the provided timestamp (inclusive).\\ncustom_fields map from strings to any", + "title": "Export \u2014 DevRev | Docs" }, { - "id": "ART-1254_KNOWLEDGE_NODE-6", - "text": "provided timestamp (inclusive).\\n\\ncreated\\\\_date.beforestringOptional`format: \"date-time\"`\\n\\nFilters for objects created before the provided timestamp\\n(inclusive).\\n\\ndisplay\\\\_namelist of stringsOptional\\n\\nArray of display names of accounts to be filtered.\\n\\nexternal\\\\_refslist of stringsOptional\\n\\nArray of references of accounts to be filtered.\\n\\nfirstintegerOptional`>=1``<=500`\\n\\nThe number of accounts to return. The default is \\'50\\'.\\n\\nmodified\\\\_date.afterstringOptional`format:", - "title": "Export Accounts | DevRev | Docs" + "id": "ART-1301_KNOWLEDGE_NODE-8", + "text": "\" : \" value \" 3 }\\nAPI Reference accounts Export.\\n\\nGET https:// api.devrev.ai / accounts.export\\nExports a collection of accounts.\\nQuery parameters.\\n\\ncreated_by string Optional\\nFilters for accounts created by the specified user(s).\\ncreated_date.after datetime Optional\\nFilters for objects created after the provided timestamp (inclusive).\\ncreated_date.before datetime Optional\\nFilters for objects created before the provided timestamp (inclusive).\\ncustom_fields map from strings to any", + "title": "Delete \u2014 DevRev | Docs" }, { - "id": "ART-1449_KNOWLEDGE_NODE-2", - "text": "user(s).\\n\\ncreated_date.afterstringOptional`format: \"date-time\"`\\n\\nFilters for objects created after the provided timestamp (inclusive).\\n\\ncreated_date.beforestringOptional`format: \"date-time\"`\\n\\nFilters for objects created before the provided timestamp (inclusive).\\n\\ndisplay_namelist of stringsOptional\\n\\nArray of display names of accounts to be filtered.\\n\\nexternal_refslist of stringsOptional\\n\\nArray of references of accounts to be filtered.\\n\\nfirstintegerOptional`>=1``<=500`\\n\\nThe", - "title": "Export Accounts \u2014 DevRev | Docs" + "id": "ART-1650_KNOWLEDGE_NODE-3", + "text": "delete.\\nResponse.\\n\\nThis endpoint returns a map from strings to any.\\nAPI Reference accounts Export.\\n\\nGET https:// api.devrev.ai / accounts.export\\nExports a collection of accounts.\\nQuery parameters.\\n\\ncreated_by string Optional\\nFilters for accounts created by the specified user(s).\\ncreated_date.after datetime Optional\\nFilters for objects created after the provided timestamp (inclusive).\\ncreated_date.before datetime Optional\\nFilters for objects created before the provided timestamp", + "title": "List Post \u2014 DevRev | Docs" }, { - "id": "ART-1652_KNOWLEDGE_NODE-12", - "text": "objects created after the provided timestamp (inclusive).\\nmodified_date.before datetime Optional\\nFilters for objects created before the provided timestamp (inclusive).\\nowned_by string Optional\\nFilters for accounts owned by the specified user(s).\\nsort_by string Optional\\nFields to sort the accounts by and the direction to sort them in.\\nstage string Optional\\nFilters for accounts on specified stages.\\ntags string Optional\\nList of tags to be filtered.\\nResponse.\\n\\nThis endpoint returns an", - "title": "Export \u2014 DevRev | Docs" + "id": "ART-1509_KNOWLEDGE_NODE-3", + "text": "delete.\\nResponse.\\n\\nThis endpoint returns a map from strings to any.\\nAPI Reference accounts Export.\\n\\nGET https:// api.devrev.ai / accounts.export\\nExports a collection of accounts.\\nQuery parameters.\\n\\ncreated_by string Optional\\nFilters for accounts created by the specified user(s).\\ncreated_date.after datetime Optional\\nFilters for objects created after the provided timestamp (inclusive).\\ncreated_date.before datetime Optional\\nFilters for objects created before the provided timestamp", + "title": "Prepare \u2014 DevRev | Docs" }, { - "id": "ART-1303_KNOWLEDGE_NODE-6", - "text": "exported accounts.\\nShow 18 properties\\nGET / accounts.export\\n$ curl -G https://api.devrev.ai/accounts.export \\\\ > -H \" Authorization: Bearer \" \\\\ > --data-urlencode created_date.after=2023-01-01T12:00:00Z \\\\ > --data-urlencode created_date.before=2023-01-01T12:00:00Z \\\\ > --data-urlencode modified_date.after=2023-01-01T12:00:00Z \\\\ > --data-urlencode modified_date.before=2023-01-01T12:00:00Z\\n200 Retrieved 1 { 2 \" accounts \" : [ 3 { 4 \" created_date \" : \" 2023-01-01T12:00:00Z \" , 5 \"", - "title": "Export Post \u2014 DevRev | Docs" + "id": "ART-1607_KNOWLEDGE_NODE-3", + "text": "delete.\\nResponse.\\n\\nThis endpoint returns a map from strings to any.\\nAPI Reference accounts Export.\\n\\nGET https:// api.devrev.ai / accounts.export\\nExports a collection of accounts.\\nQuery parameters.\\n\\ncreated_by string Optional\\nFilters for accounts created by the specified user(s).\\ncreated_date.after datetime Optional\\nFilters for objects created after the provided timestamp (inclusive).\\ncreated_date.before datetime Optional\\nFilters for objects created before the provided timestamp", + "title": "Get Post \u2014 DevRev | Docs" }, { - "id": "ART-1652_KNOWLEDGE_NODE-10", - "text": "Optional\\nFilters for accounts created by the specified user(s).\\ncreated_date.after datetime Optional\\nFilters for objects created after the provided timestamp (inclusive).\\ncreated_date.before datetime Optional\\nFilters for objects created before the provided timestamp (inclusive).\\ncursor string Optional\\nThe cursor to resume iteration from. If not provided, then iteration starts from the beginning.\\ncustom_fields map from strings to any Optional\\nFilters for custom fields.\\ndisplay_name", - "title": "Export \u2014 DevRev | Docs" + "id": "ART-1643_KNOWLEDGE_NODE-3", + "text": "delete.\\nResponse.\\n\\nThis endpoint returns a map from strings to any.\\nAPI Reference accounts Export.\\n\\nGET https:// api.devrev.ai / accounts.export\\nExports a collection of accounts.\\nQuery parameters.\\n\\ncreated_by string Optional\\nFilters for accounts created by the specified user(s).\\ncreated_date.after datetime Optional\\nFilters for objects created after the provided timestamp (inclusive).\\ncreated_date.before datetime Optional\\nFilters for objects created before the provided timestamp", + "title": "List Post \u2014 DevRev | Docs" }, { - "id": "ART-1303_KNOWLEDGE_NODE-15", - "text": "Optional\\nFilters for accounts created by the specified user(s).\\ncreated_date.after datetime Optional\\nFilters for objects created after the provided timestamp (inclusive).\\ncreated_date.before datetime Optional\\nFilters for objects created before the provided timestamp (inclusive).\\ncursor string Optional\\nThe cursor to resume iteration from. If not provided, then iteration starts from the beginning.\\ncustom_fields map from strings to any Optional\\nFilters for custom fields.\\ndisplay_name", - "title": "Export Post \u2014 DevRev | Docs" + "id": "ART-1825_KNOWLEDGE_NODE-3", + "text": "delete.\\nResponse.\\n\\nThis endpoint returns a map from strings to any.\\nAPI Reference accounts Export.\\n\\nGET https:// api.devrev.ai / accounts.export\\nExports a collection of accounts.\\nQuery parameters.\\n\\ncreated_by string Optional\\nFilters for accounts created by the specified user(s).\\ncreated_date.after datetime Optional\\nFilters for objects created after the provided timestamp (inclusive).\\ncreated_date.before datetime Optional\\nFilters for objects created before the provided timestamp", + "title": "List \u2014 DevRev | Docs" }, { - "id": "ART-1639_KNOWLEDGE_NODE-10", - "text": "Optional\\nFilters for accounts created by the specified user(s).\\ncreated_date.after datetime Optional\\nFilters for objects created after the provided timestamp (inclusive).\\ncreated_date.before datetime Optional\\nFilters for objects created before the provided timestamp (inclusive).\\ncursor string Optional\\nThe cursor to resume iteration from. If not provided, then iteration starts from the beginning.\\ncustom_fields map from strings to any Optional\\nFilters for custom fields.\\ndisplay_name", - "title": "Export Post \u2014 DevRev | Docs" + "id": "ART-1837_KNOWLEDGE_NODE-3", + "text": "delete.\\nResponse.\\n\\nThis endpoint returns a map from strings to any.\\nAPI Reference accounts Export.\\n\\nGET https:// api.devrev.ai / accounts.export\\nExports a collection of accounts.\\nQuery parameters.\\n\\ncreated_by string Optional\\nFilters for accounts created by the specified user(s).\\ncreated_date.after datetime Optional\\nFilters for objects created after the provided timestamp (inclusive).\\ncreated_date.before datetime Optional\\nFilters for objects created before the provided timestamp", + "title": "Update \u2014 DevRev | Docs" }, { - "id": "ART-1303_KNOWLEDGE_NODE-17", - "text": "objects created after the provided timestamp (inclusive).\\nmodified_date.before datetime Optional\\nFilters for objects created before the provided timestamp (inclusive).\\nowned_by string Optional\\nFilters for accounts owned by the specified user(s).\\nsort_by string Optional\\nFields to sort the accounts by and the direction to sort them in.\\nstage string Optional\\nFilters for accounts on specified stages.\\ntags string Optional\\nList of tags to be filtered.\\nResponse.\\n\\nThis endpoint returns an", - "title": "Export Post \u2014 DevRev | Docs" + "id": "ART-1597_KNOWLEDGE_NODE-3", + "text": "delete.\\nResponse.\\n\\nThis endpoint returns a map from strings to any.\\nAPI Reference accounts Export.\\n\\nGET https:// api.devrev.ai / accounts.export\\nExports a collection of accounts.\\nQuery parameters.\\n\\ncreated_by string Optional\\nFilters for accounts created by the specified user(s).\\ncreated_date.after datetime Optional\\nFilters for objects created after the provided timestamp (inclusive).\\ncreated_date.before datetime Optional\\nFilters for objects created before the provided timestamp", + "title": "Update \u2014 DevRev | Docs" }, { - "id": "ART-1639_KNOWLEDGE_NODE-12", - "text": "objects created after the provided timestamp (inclusive).\\nmodified_date.before datetime Optional\\nFilters for objects created before the provided timestamp (inclusive).\\nowned_by string Optional\\nFilters for accounts owned by the specified user(s).\\nsort_by string Optional\\nFields to sort the accounts by and the direction to sort them in.\\nstage string Optional\\nFilters for accounts on specified stages.\\ntags string Optional\\nList of tags to be filtered.\\nResponse.\\n\\nThis endpoint returns an", - "title": "Export Post \u2014 DevRev | Docs" + "id": "ART-1651_KNOWLEDGE_NODE-3", + "text": "delete.\\nResponse.\\n\\nThis endpoint returns a map from strings to any.\\nAPI Reference accounts Export.\\n\\nGET https:// api.devrev.ai / accounts.export\\nExports a collection of accounts.\\nQuery parameters.\\n\\ncreated_by string Optional\\nFilters for accounts created by the specified user(s).\\ncreated_date.after datetime Optional\\nFilters for objects created after the provided timestamp (inclusive).\\ncreated_date.before datetime Optional\\nFilters for objects created before the provided timestamp", + "title": "Create \u2014 DevRev | Docs" } ] }, @@ -1012,54 +1012,54 @@ "query": "Sales One App not visible after login", "retrievals": [ { - "id": "ART-17569_KNOWLEDGE_NODE-1", - "text": "message in the UI if they try to access an uninstalled app: \\xe2\\x80\\x9cWe can\\xe2\\x80\\x99t authorize you because of an OAuth error. For more information, contact your Salesforce administrator.\\xe2\\x80\\x9d and the OAUTH_APPROVAL_ERROR_GENERIC message.\"\\n\\nDue to this, customers may experience issues when trying to create a new Salesforce connection and install the DevRev app on their Salesforce instance.\\n\\nRead more about this on the shared article above. Follow the next steps to enable the", - "title": "Issues with Salesforce OAuth connection" + "id": "ART-4255_KNOWLEDGE_NODE-33", + "text": "\\n**Solution** : Confirm that user identification is performed before using the `showSupport()` function or XML button.\\n\\n * **Issue** : Incorrect operation due to `App ID` and `secret` misconfiguration. \\n**Solution** : Ensure correct functionality by double-checking that both `App ID` and `secret` values are accurately configured in your application or sample app.\\n\\nWas this page helpful?YesNo\\n\\n[DevRev SDK for iOSUp Next](/public/sdks/ios)\\n\\n[Built", + "title": "DevRev SDK for Android \u2014 DevRev | Docs" }, { - "id": "ART-2019_KNOWLEDGE_NODE-0", - "text": "b'Product\\nPlatform\\nSolutions\\nMarketplace\\nCompany\\nResources\\nPricing\\n\\nLogin Book a demo\\n\\nProduct\\n\\nPlatform\\n\\nSolutions\\n\\nMarketplace\\n\\nCompany\\n\\nResources\\n\\nPricing\\n\\nLogin Book a demo\\nSearch\\nCTRL + K\\n\\nIntroduction\\nAgentOS platform\\n\\nCore concepts\\nApps\\nGroups\\nParts & trails\\nVistas\\n\\nVista Reports\\n\\nTasks\\nUpdates\\nCustomer email notifications\\nRoles\\n\\nDefault privileges by group\\n\\nAccess control\\nObject customization\\nGlossary\\nSearch\\nWorkflow\\nTemplates\\nAccessing", - "title": "Smart sprint | Automate | Snap-ins | DevRev" + "id": "ART-2982_KNOWLEDGE_NODE-6", + "text": "method.\\n\\n[code]\\n\\n 1| DevRev.configure(appID: string) \\n ---|---\\n[/code] \\n \\n## Identification\\n\\nTo access certain features of the DevRev SDK, user identification is required.\\n\\nThe identification function should be placed appropriately in your app after the user logs in. If you have the user information available at app launch, call the function after the `DevRev.configure(appID:)` method.\\n\\n#####\\n\\nOn iOS, if you haven\\xe2\\x80\\x99t previously identified the user, the DevRev", + "title": "React Native integration \u2014 DevRev | Docs" }, { - "id": "ART-1947_KNOWLEDGE_NODE-1", - "text": "[Groups](/docs/product/groups)\\n + [Parts & trails](/docs/product/parts)\\n + [Vistas](/docs/product/vistas)\\n\\n - [Vista Reports](/docs/product/vista-reports)\\n - [Board view](/docs/product/board-view)\\n + [Tasks](/docs/product/tasks)\\n + [Updates](/docs/product/updates)\\n + [Customer email notifications](/docs/product/customer-emails)\\n + [Roles](/docs/product/roles)\\n\\n - [Default privileges by group](/docs/product/privs)\\n + [Access control](/docs/product/access-control)\\n +", - "title": "Apps | Computer by DevRev | DevRev" + "id": "ART-1031_KNOWLEDGE_NODE-6", + "text": "times, causing significant delays\\n\\nThe solution\\n------------\\n\\n### Visual playback of issues\\n\\nComputer, powered by agentic AI, provides product teams with a video of how users interact with the app\\xe2\\x80\\x99s login and splash screens. This visual playback aids in pinpointing where users encounter issues and identifying confusing elements. These insights are then shared with the development team, allowing for quick issue resolution and minimizing drop-offs during the onboarding", + "title": "AR Digital Wealth cuts support TAT by 60% with faster issue solving" }, { - "id": "ART-12458_KNOWLEDGE_NODE-1", - "text": "__\\n\\n[Pricing](https://devrev.ai/pricing)\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](https://devrev.ai/request-a-demo)\\n\\nOn this page\\n\\n * [Troubleshooting](/public/sdks/react-native/troubleshooting#troubleshooting)\\n\\n[SDKs](/public/sdks)[DevRev SDK for React Native and Expo](/public/sdks/react-native/quickstart)\\n\\n#\\n\\nTroubleshooting\\n\\n * **Issue** : Support chat won\\xe2\\x80\\x99t show. **Solution** : Ensure you have correctly called one of the identification methods:", - "title": "Troubleshooting \u2014 DevRev | Docs" + "id": "ART-2047_KNOWLEDGE_NODE-0", + "text": "b'Salesforce AirSync | AirSync | Snap-ins | DevRev\\n\\n* Computer\\n* Resources\\n* [Our Customers](/case-study)\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](/request-a-demo)\\n\\nComputer\\n\\nResources\\n\\n[Our Customers](/case-study)\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](/request-a-demo)\\n\\nSearch\\n\\n`CTRL`\\xc2\\xa0+\\xc2\\xa0`K`\\n\\n* [Introduction](/docs)\\n* [Computer by DevRev](/docs/intro)\\n\\n + [Core concepts](/docs/product/core)\\n + [Apps](/docs/product/apps)\\n +", + "title": "Salesforce AirSync | AirSync | Snap-ins | DevRev" }, { - "id": "ART-3109_KNOWLEDGE_NODE-1", - "text": "[Apps](/docs/product/apps)\\n + [Groups](/docs/product/groups)\\n + [Parts & trails](/docs/product/parts)\\n + [Vistas](/docs/product/vistas)\\n\\n - [Vista Reports](/docs/product/vista-reports)\\n - [Board view](/docs/product/board-view)\\n + [Tasks](/docs/product/tasks)\\n + [Updates](/docs/product/updates)\\n + [Customer email notifications](/docs/product/customer-emails)\\n + [Roles](/docs/product/roles)\\n\\n - [Default privileges by group](/docs/product/privs)\\n + [Access", - "title": "Plug widget customization | Computer for Your Customers | DevRev" + "id": "ART-17569_KNOWLEDGE_NODE-0", + "text": "b'\"Starting in early September 2025, Salesforce will restrict the use of uninstalled connected apps. This usage restriction will block end users from using uninstalled connected apps. This change is part of Salesforce\\'s commitment to making our products and services secure-by-default.\"\\n\\n[Prepare for Connected App Usage Restrictions Change](https://help.salesforce.com/s/articleView?id=005132365&type=1)\\n\\n\"If API Access control isn\\xe2\\x80\\x99t enabled, end users see the following error", + "title": "Issues with Salesforce OAuth connection" }, { - "id": "ART-1968_KNOWLEDGE_NODE-1", - "text": "[Apps](/docs/product/apps)\\n + [Groups](/docs/product/groups)\\n + [Parts & trails](/docs/product/parts)\\n + [Vistas](/docs/product/vistas)\\n\\n - [Vista Reports](/docs/product/vista-reports)\\n - [Board view](/docs/product/board-view)\\n + [Tasks](/docs/product/tasks)\\n + [Updates](/docs/product/updates)\\n + [Customer email notifications](/docs/product/customer-emails)\\n + [Roles](/docs/product/roles)\\n\\n - [Default privileges by group](/docs/product/privs)\\n + [Access", - "title": "Conversation insights | Support analytics | Computer for Support Teams | DevRev" + "id": "ART-984_KNOWLEDGE_NODE-25", + "text": "for sales visibility (or at least notifications).\\n\\nThe key is that some level of integration is necessary between systems to provide visibility without requiring people to\\nlook in different places unless you have a platform that handles these in a converged manner.\\n\\nWhy change\\n\\nThis will help facilitate the following:\\n\\n\\n Interactions are coordinated and consistent\\n Hand-offs are handled correctly\\n Customers won\\xe2\\x80\\x99t get tossed around or told different things by different", + "title": "Why you Should be Looking at Support Differently" }, { - "id": "ART-16263_KNOWLEDGE_NODE-37", - "text": "Confluence links (anonymous content cannot be tracked or mapped)\\n\\nEnabling the upload app button\\n------------------------------\\n\\nIf you do not see the **Upload App** button in Confluence Datacenter, it may be due to permission restrictions or feature disablement by your admin. To enable it:\\n\\n1. Ensure you are logged in as a **Confluence Administrator**.\\n2. Go to **Administration > Add-ons > Upload App**.\\n3. If the button is still not available:\\n * Contact your system administrator", - "title": "Confluence Datacenter AirSync | AirSync | Snap-ins | DevRev" + "id": "ART-15507_KNOWLEDGE_NODE-6", + "text": "Expo](/sdks/react-native/quickstart)\\n\\nFeatures\\n========\\n\\nCopy page\\n\\nIdentification\\n--------------\\n\\nTo access certain features of the DevRev SDK, user identification is required.\\n\\nThe identification function should be placed appropriately in your app after the user logs in. If you have the user information available at app launch, call the function after the `DevRev.configure(appID: string)` method.\\n\\n##### \\n\\nOn iOS, if you haven\\xe2\\x80\\x99t previously identified the user, the", + "title": "Features | DevRev | Docs" }, { - "id": "ART-2059_KNOWLEDGE_NODE-0", - "text": "b'Product Platform Solutions Marketplace Company Resources Pricing\\n\\nLogin Book a demo\\nProduct Platform Solutions Marketplace Company Resources Pricing\\nLogin Book a demo\\nSearch CTRL + K\\n\\nIntroduction AgentOS platform\\n\\nCore concepts Apps Groups Parts & trails Vistas Vista Reports\\nTasks Updates Customer email notifications Roles Default privileges by group\\nAccess control Object customization Glossary Search People insights Workflow Templates Accessing DevRev External identity provider", - "title": "Install PLuG chat on your website" + "id": "ART-12456_KNOWLEDGE_NODE-6", + "text": "Expo](/public/sdks/react-native/quickstart)\\n\\n#\\n\\nFeatures\\n\\n## Identification\\n\\nTo access certain features of the DevRev SDK, user identification is required.\\n\\nThe identification function should be placed appropriately in your app after the user logs in. If you have the user information available at app launch, call the function after the `DevRev.configure(appID:)` method.\\n\\n#####\\n\\nOn iOS, if you haven\\xe2\\x80\\x99t previously identified the user, the DevRev SDK will automatically", + "title": "Features \u2014 DevRev | Docs" }, { - "id": "ART-4186_KNOWLEDGE_NODE-1", - "text": "[Apps](/docs/product/apps)\\n + [Groups](/docs/product/groups)\\n + [Parts & trails](/docs/product/parts)\\n + [Vistas](/docs/product/vistas)\\n\\n - [Vista Reports](/docs/product/vista-reports)\\n - [Board view](/docs/product/board-view)\\n + [Tasks](/docs/product/tasks)\\n + [Updates](/docs/product/updates)\\n + [Customer email notifications](/docs/product/customer-emails)\\n + [Roles](/docs/product/roles)\\n\\n - [Default privileges by group](/docs/product/privs)\\n + [Access", - "title": "Computer for User Insights | Session analytics | Computer for Your Customers | DevRev" + "id": "ART-1947_KNOWLEDGE_NODE-0", + "text": "b'Apps | Computer by DevRev | DevRev\\n\\n* Computer\\n* Resources\\n* [Our Customers](/case-study)\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](/request-a-demo)\\n\\nComputer\\n\\nResources\\n\\n[Our Customers](/case-study)\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](/request-a-demo)\\n\\nSearch\\n\\n`CTRL`\\xc2\\xa0+\\xc2\\xa0`K`\\n\\n* [Introduction](/docs)\\n* [Computer by DevRev](/docs/intro)\\n\\n + [Core concepts](/docs/product/core)\\n + [Apps](/docs/product/apps)\\n +", + "title": "Apps | Computer by DevRev | DevRev" }, { - "id": "ART-1477_KNOWLEDGE_NODE-20", - "text": "it.](https://devrev.ai/blog/soc-compliance)\\n\\nProduct\\n\\n * [Build](https://devrev.ai/build)\\n * [Support](https://devrev.ai/support)\\n * [Search](https://devrev.ai/search)\\n * [PLuG - User Engagement](https://devrev.ai/plug-user-engagement)\\n * [PLuG - User Observability](https://devrev.ai/plug-observability)\\n * [Marketplace](https://marketplace.devrev.ai/)\\n\\nPlatform\\n\\n * [Airdrop](https://devrev.ai/airdrop)\\n * [Analytics](https://devrev.ai/analytics)\\n * [Workflow", - "title": "Snap-in V1 manifest \u2014 DevRev | Docs" + "id": "ART-17569_KNOWLEDGE_NODE-1", + "text": "message in the UI if they try to access an uninstalled app: \\xe2\\x80\\x9cWe can\\xe2\\x80\\x99t authorize you because of an OAuth error. For more information, contact your Salesforce administrator.\\xe2\\x80\\x9d and the OAUTH_APPROVAL_ERROR_GENERIC message.\"\\n\\nDue to this, customers may experience issues when trying to create a new Salesforce connection and install the DevRev app on their Salesforce instance.\\n\\nRead more about this on the shared article above. Follow the next steps to enable the", + "title": "Issues with Salesforce OAuth connection" } ] }, @@ -1068,54 +1068,54 @@ "query": "linking tickets and issues for analytics", "retrievals": [ { - "id": "ART-4184_KNOWLEDGE_NODE-4", - "text": "analytics](/docs/product/support-analytics)\\n\\n - [Conversation insights](/docs/dashboards/conversation-insights)\\n - [Conversation-SLA Analytics](/docs/dashboards/conversation-sla-analytics)\\n - [Conversation-Team Performance](/docs/dashboards/conversation-team-performance)\\n - [Ticket insights](/docs/dashboards/ticket-insights)\\n - [Ticket-SLA Analytics](/docs/dashboards/ticket-sla-analytics)\\n - [Ticket-Team Performance](/docs/dashboards/ticket-team-performance)\\n +", - "title": "Ticket linked issues comment sync | Automate | Snap-ins | DevRev" + "id": "ART-15664_KNOWLEDGE_NODE-13", + "text": "\\n\\nYou may want to restrict links to specific subtypes of objects. For example, only allowing issues\\nof a particular subtype to be linked to tickets.\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl --location \\'https://api.devrev.ai/link-types.custom.create\\' \\\\ |\\n| > | --header \\'Content-Type: application/json\\' \\\\ |\\n| > | --header \\'Authorization: Bearer \\' \\\\ |\\n| > | --data \\'{ |\\n| > | \"name\": \"Link between social media issues and tickets\", |\\n| > | \"source_types\": [ |\\n| > | { |\\n|", + "title": "Links | DevRev | Docs" }, { - "id": "ART-1972_KNOWLEDGE_NODE-16", - "text": "sync](/docs/automations/ticket-linked-issues-comment-sync)\\n - [Slack message agent](/docs/automations/slack-message-agent)\\n + [Integrate](/docs/integrate)\\n\\n - [Bitbucket](/docs/integrations/bitbucket)\\n - [Calendly](/docs/integrations/calendly)\\n - [Coralogix security integration](/docs/integrations/coralogix)\\n - [Datadog](/docs/integrations/datadog)\\n - [Google Calendar AirSync](/docs/integrations/google-calendar-airdrop)\\n - [Email](/docs/integrations/email)\\n\\n", - "title": "Ticket-SLA Analytics | Support analytics | Computer for Support Teams | DevRev" + "id": "ART-15716_KNOWLEDGE_NODE-8", + "text": "for TicketsWe have a summarize option (it would resemble sparkle symbol) in the top right corner of the ticket view, which uses the ticket content to summarize the ticket\\n\\n7. Difference between Issues and Tickets\\n\\nTickets\\xc2\\xa0are for customer support\\xe2\\x80\\x94tracking requests, problems, or questions from customers or prospects.\\n\\nIssues\\xc2\\xa0are internal work items for developers\\xe2\\x80\\x94used to improve the product, fix bugs, or implement features. Issues can be linked to", + "title": "Support queries related playbook" }, { - "id": "ART-1979_KNOWLEDGE_NODE-39", - "text": "other tickets or issues that relate to this ticket, click **Link Records** and select the relevant items.\\n7. If you would like to immediately create another ticket, select **Create multiple**.\\n8. Click **Create**.\\n\\nIf a ticket is created from an existing conversation, then the ticket's title and description are populated automatically from the conversation.\\n\\n![]()\\n\\nYou can create a child issue by clicking **+ Link issue** > **Add a child issue**. You can link the other existing issue as", + "id": "ART-1979_KNOWLEDGE_NODE-60", + "text": "tickets\\n-----------------\\n\\nFollow up tickets allow support teams to seamlessly address unresolved issues, recurring problems, or additional concerns without losing context. By linking follow-up tickets to the original ticket(archived/immutable), teams can track ongoing issues more effectively, minimize duplicate work and enhance customer experience. A follow-up ticket is a new ticket that is created and linked when a customer responds in reference to an archived/immutable ticket. The", "title": "Tickets | Computer for Support Teams | DevRev" }, { - "id": "ART-15664_KNOWLEDGE_NODE-17", - "text": "exhaustive list.\\n\\n### Links from tickets\\n\\nLinks from tickets\\n\\ntarget\\n\\nsource\\n\\nis dependent on\\n\\nis related to\\n\\nis related to\\n\\nis parent of\\n\\nis merged into\\n\\nticket\\n\\nissue\\n\\nticket\\n\\narticle\\n\\n##### \\n\\nOnly ticket \\xe2\\x86\\x92 issue is allowed for creating a link with \\xe2\\x80\\x9cis dependent on\\xe2\\x80\\x9d. Creating the link in reverse (issue \\xe2\\x86\\x92 ticket) is not possible; however, you can swap the source and target objects to achieve the same result.\\n\\n### Links", - "title": "Links | DevRev | Docs" + "id": "ART-10697_KNOWLEDGE_NODE-30", + "text": "New filtering options let agents view tickets tied to specific articles, while updated analytics reveal the most and least linked articles, improving knowledge sharing and support strategy.\\n* Plug is our live chat widget designed for real-time conversations in your customer portal. It reduces ticket volume by resolving common queries instantly, enhancing self-service and speeding up issue resolution. Use spotlight cards or banners to notify customers about incidents, updates, or promotions,", + "title": "February 2025 | Changelog | DevRev" }, { - "id": "ART-1002_KNOWLEDGE_NODE-3", - "text": "systems being used for engineering work are commonly abused by sales, marketing and support teams. For example, a sales rep may create an issue for a developer for a customer request. In the case of support, you\\xe2\\x80\\x99ll commonly see a ton of duplicate issues when only one was really necessary. This leads to a lot of noise for developers, and devalues the notion of an \\xe2\\x80\\x9cissue\\xe2\\x80\\x9d. By keeping a clear line between tickets and issues, we ensure the following:\\n\\n\\n issues", - "title": "Tickets, Issues: When to Use Each" + "id": "ART-2009_KNOWLEDGE_NODE-26", + "text": "*Prioritized* but no issues are linked.\\n* Post to ticket's timeline mentioning its owners when it is moved to *Product Assist* stage.\\n* Post to linked ticket's timelines when enhancement changes stage.\\n* Notify target close date to ticket, issue, tasks, opportunity and enhancement owners.\\n* Notify enhancement owners for linking PRD and design docs.\\n* Post a message on part timeline tagging part owners when a new ticket is linked to that part.\\n* Post in the linked conversation when a", + "title": "Convergence | Automate | Snap-ins | DevRev" }, { - "id": "ART-4184_KNOWLEDGE_NODE-15", - "text": "[Operational SLA Metrics](/docs/automations/operational-sla-metrics)\\n - [Custom field migration](/docs/automations/custom-field-migration)\\n - [Slack scraper](/docs/automations/slack-scraper)\\n - [Slack Broadcaster](/docs/automations/slack-broadcaster)\\n - [Reported by enricher](/docs/automations/ticket-reported-by)\\n - [Ticket approval workflow](/docs/automations/ticket-approval-workflow)\\n - [Ticket linked issues comment", - "title": "Ticket linked issues comment sync | Automate | Snap-ins | DevRev" + "id": "ART-15617_KNOWLEDGE_NODE-5", + "text": "prompts\\n\\nKnowledge Management : Tracks gaps in knowledge base to improve training data\\n\\nLimitation : Analytics solely tied to tickets, lacking product and customer insights Competitive Positioning Analysis Key Differentiators (Swords)\\n\\nSword 1: Incomplete Context for Support Teams\\n\\nPylon\\'s ticketing system operates in isolation, lacking crucial context from product, customer, and engineering data, which leaves teams unable to solve problems quickly or identify and prevent recurring", + "title": "Pylon - Competitive - for the PLuG on website" }, { - "id": "ART-2012_KNOWLEDGE_NODE-4", - "text": "Analytics](/docs/dashboards/ticket-sla-analytics?)\\n * [Ticket-Team Performance](/docs/dashboards/ticket-team-performance?)\\n\\n * [Conversations](/docs/product/conversation?)\\n\\n * [Convert Conversations to Tickets](/docs/product/Conversation-Tickets?)\\n\\n * [Tickets](/docs/product/tickets?)\\n * [Routing](/docs/product/routing?)\\n * [Support best practices](/docs/product/support-bp?)\\n * [Customer portal](/docs/product/support-portal?)\\n * [Questions &", - "title": "Follow-up ticket | Automate | Snap-ins | DevRev" + "id": "ART-16803_KNOWLEDGE_NODE-26", + "text": "Tickets\\n* Meetings\\n* Objects linked to issues\\n* Users\\n\\nTo configure a workspace object loop:\\n\\n1. On the **workflow canvas**, add an action step named **Loop for [Object]**, where [Object] is the entity you want to iterate over.\\n2. Apply **filter conditions** to refine the set of objects included in the loop and perform operations on them.\\n\\nAll **actions** inside the loop execute once per object that satisfies the filter conditions.\\n\\n### For Each\\n\\nThe **For Each** loop iterates", + "title": "Workflow nodes | Workflows | Computer by DevRev | DevRev" }, { - "id": "ART-1975_KNOWLEDGE_NODE-28", - "text": "conversations against standalone tickets.\\n* **Tickets linked to issues**\\n\\n The percentage of tickets linked to product issues.\\n* **Active tickets by owner**\\n\\n The number of Open or In Progress tickets grouped by owner.\\n* **Tickets created vs. closed**\\n\\n The trend of tickets created against those closed.\\n\\nCustomer satisfaction (CSAT)\\n----------------------------\\n\\n* **CSAT score distribution**\\n\\n A distribution of customer satisfaction scores on tickets.\\n\\nTime spent per", - "title": "Ticket insights | Support analytics | Computer for Support Teams | DevRev" + "id": "ART-2048_KNOWLEDGE_NODE-27", + "text": "allows you to create parent/child relationships between issues, you cannot do the same with tickets. If your workflow requires manual creation of parent/child relationships in DevRev work items, you should use issues. If that is not a requirement and tickets are preferred for another reason, you can specify tickets as the target for ClickUp tasks.\\n\\nImport from ClickUp\\n-------------------\\n\\nFollow the steps below to import from ClickUp:\\n\\n1. In **Marketplace**, search for **ClickUp** and", + "title": "ClickUp AirSync | AirSync | Snap-ins | DevRev" }, { - "id": "ART-15664_KNOWLEDGE_NODE-14", - "text": "> | \"leaf_type\": \"issue\", |\\n| > | \"subtype\": \"social_media\" |\\n| > | } |\\n| > | ], |\\n| > | \"target_types\": [ |\\n| > | { |\\n| > | \"leaf_type\": \"ticket\" |\\n| > | } |\\n| > | ], |\\n| > | \"forward_name\": \"is related to\", |\\n| > | \"backward_name\": \"is related to\" |\\n| > | }\\' |\\n```\\n\\nThis configuration:\\n\\n* Allows issues of subtype \\xe2\\x80\\x9csocial\\\\_media\\xe2\\x80\\x9d to be linked to tickets\\n* Rejects attempts to link issues with no subtype or with other subtypes\\n\\n##### \\n\\nThe subtype", - "title": "Links | DevRev | Docs" + "id": "ART-15617_KNOWLEDGE_NODE-14", + "text": "Analytics\\n\\nDevRev : Analytics on custom objects with comprehensive product and customer insights\\n\\nDevRev : Built-in incident management and proactive issue prevention\\n\\nPylon : Strong dashboard creation but analytics limited to ticket data only Feature Comparison Matrix\\n\\nFeature\\n\\nDevRev\\n\\nPylon\\n\\nAI agents with reasoning\\n\\n\\xe2\\x9c\\x85\\n\\n\\xe2\\x9d\\x8c\\n\\nAI search on external data\\n\\n\\xe2\\x9c\\x85\\n\\n\\xe2\\x9d\\x8c\\n\\nAI-powered clustering\\n\\n\\xe2\\x9c\\x85\\n\\n\\xe2\\x9d\\x8c\\n\\nAI", + "title": "Pylon - Competitive - for the PLuG on website" }, { - "id": "ART-4184_KNOWLEDGE_NODE-5", - "text": "[Conversations](/docs/product/conversation)\\n\\n - [Conversation to ticket conversion](/docs/product/conversation-ticket)\\n + [Tickets](/docs/product/tickets)\\n + [Routing](/docs/product/routing)\\n + [Support best practices](/docs/product/support-bp)\\n + [Customer portal](/docs/product/support-portal)\\n + [Questions & answers](/docs/product/qa)\\n + [Knowledge Base](/docs/product/knowledge-base)\\n\\n - [Articles](/docs/product/articles)\\n - [Collections](/docs/product/collection)\\n", - "title": "Ticket linked issues comment sync | Automate | Snap-ins | DevRev" + "id": "ART-15664_KNOWLEDGE_NODE-6", + "text": "you want to establish a parent-child relationship between tickets and a custom object\\ntype called \\xe2\\x80\\x9cCampaign\\xe2\\x80\\x9d. This relationship helps track which tickets are assigned to which campaigns.\\n\\nTo create this relationship, make an API call to create a link type:\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl --location \\'https://api.devrev.ai/link-types.custom.create\\' \\\\ |\\n| > | --header \\'Content-Type: application/json\\' \\\\ |\\n| > | --header \\'Authorization: Bearer \\'", + "title": "Links | DevRev | Docs" } ] }, @@ -1124,54 +1124,54 @@ "query": "Data residency compliance for international customers", "retrievals": [ { - "id": "ART-888_KNOWLEDGE_NODE-42", - "text": "spaces under your sole control.How we transfer information we collect internationallyInternational transfers of information we collectWe collect information globally and may transfer, process and store your information outside of your country of residence, to wherever we or our third-party service providers operate for the purpose of providing you the Services. Whenever we transfer your information, we take steps to protect it.International transfers within the DevRev Companies: To facilitate", - "title": "Privacy Policy" + "id": "ART-12476_KNOWLEDGE_NODE-1", + "text": "designed to meet GDPR and SOC 2 compliance requirements, with controls in place to support your data privacy needs.\\n\\nAdvanced enterprise login: Seamless SAML compliance for all enterprise logins regardless of your SSO provider.\\n\\nRegional data residency options: We offer data residency options in Europe, Australia, US East (Virginia), and India, with logical data isolation and access control features.\\n\\nSelf-serve user management: Easily add or remove users from your workspace and manage", + "title": "The Future of Sessions - Powered By DevRev" }, { - "id": "ART-4174_KNOWLEDGE_NODE-11", - "text": "(EEA) is adequately protected, even when transferred to countries that may not offer an equivalent level of data protection.\\n\\n### UK-Specific Clauses\\n\\nFollowing Brexit, we also apply tailored safeguards for personal data transferred from the United Kingdom. We leverage the UK\\xe2\\x80\\x99s International Data Transfer Addendum to the EU SCCs, which ensures compliance with UK-specific data transfer requirements and aligns with the standards established by the UK\\xe2\\x80\\x99s Information", - "title": "Data Processing Agreement | DevRev" + "id": "ART-1771_KNOWLEDGE_NODE-14", + "text": "95%](/case-study/icici-prudential-life)\\n\\nChoose another country or region to see content specific to your location.\\n\\n\\xf0\\x9f\\x8c\\x8e English\\xf0\\x9f\\x87\\xaf\\xf0\\x9f\\x87\\xb5 Japanese\\n\\n[Enterprise grade security to protect customer data\\n\\nLearn more about it.\\n\\n![]()](/blog/soc-compliance)\\n\\nComputer\\n\\n* [Meet Computer](/meet-computer)\\n* [How Computer works](/how-computer-works)\\n\\nApps\\n\\n* [For Support Teams](/for-support-teams)\\n* [For Builders](/for-builders)\\n* [For", + "title": "ToughTrucksForKids.com achieves dramatic efficiency gains and customer satisfaction through AI-powered support automation" }, { - "id": "ART-4174_KNOWLEDGE_NODE-12", - "text": "Commissioner\\xe2\\x80\\x99s Office (ICO).\\n\\n### United States Data Transfer Mechanisms\\n\\nFor personal data transfers to the United States, DevRev employs recognized contractual frameworks and implements additional measures, as necessary, to safeguard your information in accordance with evolving U.S. data protection guidelines. We work to align with relevant standards and best practices to address regulatory considerations around cross-border data transfers.\\n\\n### What about Personal Data use", - "title": "Data Processing Agreement | DevRev" + "id": "ART-1772_KNOWLEDGE_NODE-15", + "text": "95%](/case-study/icici-prudential-life)\\n\\nChoose another country or region to see content specific to your location.\\n\\n\\xf0\\x9f\\x8c\\x8e English\\xf0\\x9f\\x87\\xaf\\xf0\\x9f\\x87\\xb5 Japanese\\n\\n[Enterprise grade security to protect customer data\\n\\nLearn more about it.\\n\\n![]()](/blog/soc-compliance)\\n\\nComputer\\n\\n* [Meet Computer](/meet-computer)\\n* [How Computer works](/how-computer-works)\\n\\nApps\\n\\n* [For Support Teams](/for-support-teams)\\n* [For Builders](/for-builders)\\n* [For", + "title": "Rocketium brings agility to product development through a unified platform" }, { - "id": "ART-4183_KNOWLEDGE_NODE-1", - "text": "More](https://cdn.sanity.io/files/umrbtih2/development/8c3ab1aef7fee37a816c3116a89b08b5db2ba541.pdf)\\n\\nDeveloping and maintaining an incident response plan that includes subprocessors\\xe2\\x80\\x99 roles in managing data breaches.\\n\\n![]()\\n\\nChoose another country or region to see content specific to your location.\\n\\n\\xf0\\x9f\\x8c\\x8e English\\xf0\\x9f\\x87\\xaf\\xf0\\x9f\\x87\\xb5 Japanese\\n\\n[Enterprise grade security to protect customer data\\n\\nLearn more about", - "title": "Security Subprocessors - GDPR Compliance | DevRev" + "id": "ART-15682_KNOWLEDGE_NODE-13", + "text": "experiences through session intelligence](/case-study/bajaj-finserv)\\n\\nChoose another country or region to see content specific to your location.\\n\\n\\xf0\\x9f\\x8c\\x8e English\\xf0\\x9f\\x87\\xaf\\xf0\\x9f\\x87\\xb5 Japanese\\n\\n[Enterprise grade security to protect customer data\\n\\nLearn more about it.\\n\\n![]()](/blog/soc-compliance)\\n\\nComputer\\n\\n* [Meet Computer](/meet-computer)\\n* [How Computer works](/how-computer-works)\\n\\nApps\\n\\n* [For Support Teams](/for-support-teams)\\n* [For", + "title": "L&T financial services advances digital banking with enhanced observability" }, { - "id": "ART-4174_KNOWLEDGE_NODE-10", - "text": "data privacy laws. To support this commitment, we use industry-standard frameworks and legal instruments to facilitate the lawful and secure transfer of personal data across borders.\\n\\n### EU Standard Contractual Clauses (SCCs)\\n\\nFor data transfers involving EU-based users, DevRev relies on the EU Standard Contractual Clauses (SCCs). These clauses, approved by the European Commission, provide contractual safeguards to ensure that personal data transferred outside the European Economic Area", + "id": "ART-4174_KNOWLEDGE_NODE-9", + "text": "behalf, as well as explanations on how such parties safeguard your data.\\n* **Standard Contractual clauses and other country specific clauses:** Our DPA also includes the EU Commission's Standard Contractual clausesand other country specific clauses for transferring and processing data outside of the EEA, UK and USA.\\n\\n### How does DevRev handle International Data transfers?\\n\\nAt DevRev, we understand the importance of securely managing international data transfers in compliance with global", "title": "Data Processing Agreement | DevRev" }, { - "id": "ART-888_KNOWLEDGE_NODE-43", - "text": "our global operations, we transfer information globally and allow access to that information from countries in which the DevRev owned or operated companies and have operations for the purposes described in this policy. These countries may not have equivalent privacy and data protection laws to the laws of many of the countries where our customers and users are based. When we share information about you within and among DevRev corporate affiliates, we make use of standard contractual data", - "title": "Privacy Policy" + "id": "ART-4197_KNOWLEDGE_NODE-4", + "text": "More\\n\\nChoose another country or region to see content specific to your location.\\n\\n\\xf0\\x9f\\x8c\\x8e English\\xf0\\x9f\\x87\\xaf\\xf0\\x9f\\x87\\xb5 Japanese\\n\\n[Enterprise grade security to protect customer dataLearn more about it.](/blog/soc-compliance)\\n\\nProduct\\n\\n * [Build](/build)\\n * [Support](/support)\\n * [Search](/search)\\n * [PLuG - User Engagement](/plug-user-engagement)\\n * [PLuG - User Observability](/plug-observability)\\n *", + "title": "DevRev AgentOS Pricing | Pricing made simple" }, { - "id": "ART-4174_KNOWLEDGE_NODE-9", - "text": "behalf, as well as explanations on how such parties safeguard your data.\\n* **Standard Contractual clauses and other country specific clauses:** Our DPA also includes the EU Commission's Standard Contractual clausesand other country specific clauses for transferring and processing data outside of the EEA, UK and USA.\\n\\n### How does DevRev handle International Data transfers?\\n\\nAt DevRev, we understand the importance of securely managing international data transfers in compliance with global", - "title": "Data Processing Agreement | DevRev" + "id": "ART-2043_KNOWLEDGE_NODE-31", + "text": "security to protect customer data\\n\\nLearn more about it.\\n\\n![]()](/blog/soc-compliance)\\n\\nComputer\\n\\n* [Meet Computer](/meet-computer)\\n* [How Computer works](/how-computer-works)\\n\\nApps\\n\\n* [For Support Teams](/for-support-teams)\\n* [For Builders](/for-builders)\\n* [For Customers](/for-customers)\\n* [For User Insights](/for-user-insights)\\n* [Marketplace](https://marketplace.devrev.ai/)\\n\\nResources\\n\\n* [Blog](/blog)\\n* [Our Customers](/case-study)\\n* [Snap-In", + "title": "Glean | Integrate | Snap-ins | DevRev" }, { - "id": "ART-4174_KNOWLEDGE_NODE-8", - "text": "we implement to keep your data secure, such as encryption, access controls, and regular security audits.\\n* **Data Subject Rights:** Information on how we support you in responding to requests from individuals to exercise their rights under data protection laws.\\n* **Data Transfer:** Terms regarding international data transfers, ensuring compliance with GDPR and other regulatory frameworks.\\n* **Subprocessors:** A list of any third parties we partner we engage in order to process data on your", - "title": "Data Processing Agreement | DevRev" + "id": "ART-5011_KNOWLEDGE_NODE-36", + "text": "security to protect customer data\\n\\nLearn more about it.\\n\\n![]()](/blog/soc-compliance)\\n\\nComputer\\n\\n* [Meet Computer](/meet-computer)\\n* [How Computer works](/how-computer-works)\\n\\nApps\\n\\n* [For Support Teams](/for-support-teams)\\n* [For Builders](/for-builders)\\n* [For Customers](/for-customers)\\n* [For User Insights](/for-user-insights)\\n* [Marketplace](https://marketplace.devrev.ai/)\\n\\nResources\\n\\n* [Blog](/blog)\\n* [Our Customers](/case-study)\\n* [Snap-In", + "title": "Zoho Projects AirSync | AirSync | Snap-ins | DevRev" }, { - "id": "ART-4174_KNOWLEDGE_NODE-15", - "text": "the GDPR as well as any other specific local legal requirements.\\n\\n### What about data security?\\n\\nWe have implemented industry standard organisational and other security like SOC-II certification to keep your data safe.\\n\\nYou can find out more about the security measures we employ by following this [link](https://security.devrev.ai/).\\n\\n### Reach out to us with any additional questions.\\n\\nShould you have any additional questions about privacy and data processing at DevRev, our data", - "title": "Data Processing Agreement | DevRev" + "id": "ART-15688_KNOWLEDGE_NODE-31", + "text": "to protect customer data\\n\\nLearn more about it.\\n\\n![]()](/blog/soc-compliance)\\n\\nComputer\\n\\n* [Meet Computer](/meet-computer)\\n* [How Computer works](/how-computer-works)\\n\\nApps\\n\\n* [For Support Teams](/for-support-teams)\\n* [For Builders](/for-builders)\\n* [For Customers](/for-customers)\\n* [For User Insights](/for-user-insights)\\n* [Marketplace](https://marketplace.devrev.ai/)\\n\\nResources\\n\\n* [Blog](/blog)\\n* [Our Customers](/case-study)\\n* [Snap-In", + "title": "Effort logger | Automate | Snap-ins | DevRev" }, { - "id": "ART-4183_KNOWLEDGE_NODE-4", - "text": "Policy](/legal/cookie-policy)\\n* [Privacy Policy](/legal/privacy-policy)\\n* [Terms of Service](/legal/terms-of-service)\\n\\n[System Status](/status)\\n\\n\\xc2\\xa9 2025 DevRev Inc.'", - "title": "Security Subprocessors - GDPR Compliance | DevRev" + "id": "ART-1040_KNOWLEDGE_NODE-2", + "text": "to protect customer data\\n\\nLearn more about it.\\n\\n![]()](/blog/soc-compliance)\\n\\nComputer\\n\\n* [Meet Computer](/meet-computer)\\n* [How Computer works](/how-computer-works)\\n\\nApps\\n\\n* [For Support Teams](/for-support-teams)\\n* [For Builders](/for-builders)\\n* [For Customers](/for-customers)\\n* [For User Insights](/for-user-insights)\\n* [Marketplace](https://marketplace.devrev.ai/)\\n\\nResources\\n\\n* [Blog](/blog)\\n* [Our Customers](/case-study)\\n* [Snap-In", + "title": "https://devrev.ai/case-study/bigbasket" } ] }, @@ -1180,54 +1180,54 @@ "query": "declarative pathing within the bot", "retrievals": [ { - "id": "ART-1950_KNOWLEDGE_NODE-5", - "text": "ticket conversion](/docs/product/conversation-ticket)\\n + [Tickets](/docs/product/tickets)\\n + [Routing](/docs/product/routing)\\n + [Support best practices](/docs/product/support-bp)\\n + [Customer portal](/docs/product/support-portal)\\n + [Questions & answers](/docs/product/qa)\\n + [Knowledge Base](/docs/product/knowledge-base)\\n\\n - [Articles](/docs/product/articles)\\n - [Collections](/docs/product/collection)\\n + [Turing AI agent](/docs/product/conversational-bot)\\n\\n - [Best", - "title": "Parts & trails | Computer by DevRev | DevRev" + "id": "ART-17649_KNOWLEDGE_NODE-3", + "text": "both agents and customers\\n* Complex requirements spanned agent, customer, and manager experiences\\n* Need for sophisticated routing, views, dashboards, and deterministic bot flows\\n\\nThe solution: switching to DevRev\\n---------------------------------\\n\\nThe company chose DevRev for its Computer capabilities and customization features:\\n\\n* Implementation of multiple dev organizations within DevRev\\n* Complete replacement of their previous Intercom-based support system\\n* Implementation of", + "title": "Leading APAC fintech transforms support with multi-instance AI solution" }, { - "id": "ART-12391_KNOWLEDGE_NODE-6", - "text": "+ [Turing AI agent](/docs/product/conversational-bot)\\n\\n - [Best practices for documentation that supports AI](/docs/product/writing-bp)\\n + [Commands](/docs/product/commands)\\n + [Service-level agreement](/docs/product/sla)\\n + [Operational-level agreement](/docs/product/ola)\\n + [Support snap-ins](/docs/product/snapins-support)\\n* [Computer for Builders](/docs/product/build)\\n\\n + [Issues](/docs/product/issues)\\n + [Now, Next, Later](/docs/product/nnl)\\n + [Sprint", - "title": "Conversational workflows | Workflows | Computer by DevRev | DevRev" + "id": "ART-17649_KNOWLEDGE_NODE-4", + "text": "sophisticated routing mechanisms\\n* Custom views and dashboards for different stakeholders\\n* Deterministic bot flow to guide customers through support experiences\\n* Comprehensive e2e testing to ensure reliability\\n\\n#### *We needed different instances on different paths of our website with separate memory and appearances. DevRev's architecture made this possible through multiple dev organizations.*\\xe2\\x80\\x9d\\n\\nThe impact\\n----------\\n\\n### Multiple customized support channels\\n\\nDevRev", + "title": "Leading APAC fintech transforms support with multi-instance AI solution" }, { - "id": "ART-1996_KNOWLEDGE_NODE-5", - "text": "ticket conversion](/docs/product/conversation-ticket)\\n + [Tickets](/docs/product/tickets)\\n + [Routing](/docs/product/routing)\\n + [Support best practices](/docs/product/support-bp)\\n + [Customer portal](/docs/product/support-portal)\\n + [Questions & answers](/docs/product/qa)\\n + [Knowledge Base](/docs/product/knowledge-base)\\n\\n - [Articles](/docs/product/articles)\\n - [Collections](/docs/product/collection)\\n + [Turing AI agent](/docs/product/conversational-bot)\\n\\n - [Best", - "title": "Roadmap | Computer for Builders | DevRev" + "id": "ART-1277_KNOWLEDGE_NODE-8", + "text": "1 | version: \"2\" |\\n| 2 | |\\n| 3 | name: Sample snap-in |\\n| 4 | description: Snap-in to add comments for demonstration purpose. |\\n| 5 | |\\n| 6 | service_account: |\\n| 7 | display_name: \"DevRev Bot\" |\\n```\\n\\n[3](/snapin-development/tutorials/triggered-event#event-source)\\n\\n### Event source\\n\\nFollowing the manifest update, the next step is to incorporate the [event source](/snapin-development/references/event-sources).\\nFor this scenario, events from DevRev are essential. Therefore, an", + "title": "Snap-in triggered by a DevRev event | DevRev | Docs" }, { - "id": "ART-1987_KNOWLEDGE_NODE-28", - "text": "Computer either creates a ticket or routes the conversation using the relevant routing rule.\\n\\n![]()\\n\\nGoal-oriented mode (Beta)\\n-------------------------\\n\\nThe goal-oriented agent allows users to create complete workflows triggered by their actions.\\n\\nGoal-oriented mode is currently in beta. Contact our support team for more information.\\n\\n[PreviousCollections](/docs/product/collection)[NextBest practices for documentation that supports AI](/docs/product/writing-bp)\\n\\n#### On this", - "title": "Turing AI agent | Computer for Support Teams | DevRev" + "id": "ART-1959_KNOWLEDGE_NODE-28", + "text": "of the ticket/issue/enhancement or title. | in:title crm in:title \"crm exp\" in:title crm exp in:body \"bot issues\" |\\n| type: | Enables users to filter by object type. Supported object types include: issue, enhancement, ticket, revu (for searching contacts), question\\\\_answer, conversation, article, devu (for searching internal contacts), account, feature, runnable. | type:issue type:enhancement in:title CRM type:revu type:enhancement, opportunity type:issue, enhancement", + "title": "Search | Computer by DevRev | DevRev" }, { - "id": "ART-1950_KNOWLEDGE_NODE-6", - "text": "practices for documentation that supports AI](/docs/product/writing-bp)\\n + [Commands](/docs/product/commands)\\n + [Service-level agreement](/docs/product/sla)\\n + [Operational-level agreement](/docs/product/ola)\\n + [Support snap-ins](/docs/product/snapins-support)\\n* [Computer for Builders](/docs/product/build)\\n\\n + [Issues](/docs/product/issues)\\n + [Now, Next, Later](/docs/product/nnl)\\n + [Sprint mode](/docs/product/sprint)\\n + [Enhancements](/docs/product/enhancements)\\n +", - "title": "Parts & trails | Computer by DevRev | DevRev" + "id": "ART-1485_KNOWLEDGE_NODE-12", + "text": "descriptive overview that is visible to users, offering context about the snap-in\\xe2\\x80\\x99s purpose.\\n\\n[code]\\n\\n 1| version: \"2\" \\n ---|--- \\n 2| \\n 3| name: Sample snap-in \\n 4| description: Snap-in to add comments for demonstration purpose. \\n 5| \\n 6| service_account: \\n 7| display_name: \"DevRev Bot\"\\n[/code] \\n \\n[3](/public/snapin-development/tutorials/triggered-event#event-source)\\n\\n### Event source\\n\\nFollowing the manifest update, the next step", + "title": "Snap-in triggered by a DevRev event \u2014 DevRev | Docs" }, { - "id": "ART-12394_KNOWLEDGE_NODE-6", - "text": "+ [Turing AI agent](/docs/product/conversational-bot)\\n\\n - [Best practices for documentation that supports AI](/docs/product/writing-bp)\\n + [Commands](/docs/product/commands)\\n + [Service-level agreement](/docs/product/sla)\\n + [Operational-level agreement](/docs/product/ola)\\n + [Support snap-ins](/docs/product/snapins-support)\\n* [Computer for Builders](/docs/product/build)\\n\\n + [Issues](/docs/product/issues)\\n + [Now, Next, Later](/docs/product/nnl)\\n + [Sprint", - "title": "Workflow management | Workflows | Computer by DevRev | DevRev" + "id": "ART-15716_KNOWLEDGE_NODE-14", + "text": "AI Bot \\xe2\\x80\\x93 Turing\\n\\nYes! DevRev offers an AI-powered assistant called Turing , which can answer questions, suggest articles, summarize conversations, and more. You can read more about it in the documentation: [https://docs.devrev.ai/product/conversational-bot](https://docs.devrev.ai/product/conversational-bot)\\n\\n4.\\xe2\\x80\\x82Difference Between Runnables and Features\\n\\nA feature is a unit of configuration or capability in the product, often representing a user-facing function or", + "title": "Support queries related playbook" }, { - "id": "ART-12391_KNOWLEDGE_NODE-29", - "text": "type that causes the agent to pause (for example, DevUser). |\\n| additional\\\\_context (optional) | String | Additional context you want to pass to the agent for more personalized responses. You can also use variables from previous steps here. |\\n\\n![]()\\n\\n* Each button creates a corresponding output port in the workflow.\\n* When a button is clicked, the original message is updated to remove the\\n buttons.\\n* A confirmation message is added showing which option was", - "title": "Conversational workflows | Workflows | Computer by DevRev | DevRev" + "id": "ART-1954_KNOWLEDGE_NODE-34", + "text": "page.\\n4. Under the **Bots and Snap-ins Notification** panel, manage bots and snap-ins notifications. These override default notifications.\\n\\n![]()\\n\\nCurrently, all customer messages are treated as comments and share the same priority.\\n\\nCollision and prioritization\\n----------------------------\\n\\nDevRev prioritizes actions (comments, mentions, assignments, etc.) over actors (bots) to ensure efficiency and reduce noise. This means that the priority and channel of notifications are", + "title": "Updates | Computer by DevRev | DevRev" }, { - "id": "ART-12390_KNOWLEDGE_NODE-6", - "text": "+ [Turing AI agent](/docs/product/conversational-bot)\\n\\n - [Best practices for documentation that supports AI](/docs/product/writing-bp)\\n + [Commands](/docs/product/commands)\\n + [Service-level agreement](/docs/product/sla)\\n + [Operational-level agreement](/docs/product/ola)\\n + [Support snap-ins](/docs/product/snapins-support)\\n* [Computer for Builders](/docs/product/build)\\n\\n + [Issues](/docs/product/issues)\\n + [Now, Next, Later](/docs/product/nnl)\\n + [Sprint", - "title": "Workflow action library | Workflows | Computer by DevRev | DevRev" + "id": "ART-4199_KNOWLEDGE_NODE-26", + "text": "and copy the signing secret.\\n3. Go to **OAuth & Permissions** and add the following scopes under **Bot Token Scopes**.\\n * channels:history\\n * chat:write\\n * files:read\\n * metadata.message:read\\n * team:read\\n * usergroups:read\\n * users:read\\n * users:read.email\\n4. Once the scopes are updated, copy the **Bot User OAuth Token** and click the button below it.\\n5. Go to **Event Subscriptions** and click **Enable Events**.\\n6. Under **Subscribe to bot events**, add", + "title": "Slack message agent | Automate | Snap-ins | DevRev" }, { - "id": "ART-1950_KNOWLEDGE_NODE-12", - "text": "Node](/docs/automations/search-node)\\n - [Sentiment evaluator](/docs/automations/sentiment-evaluator)\\n - [Subtype Migration](/docs/automations/subtype-migration)\\n - [Real-time sentiment evaluator](/docs/automations/realtime-sentiment-evaluator)\\n - [Send customized emails](/docs/automations/send-emails)\\n - [StageFlow automator](/docs/automations/stageflow-automator)\\n - [Smart issue creator](/docs/automations/smart-issue-creator)\\n - [Set user preference for", - "title": "Parts & trails | Computer by DevRev | DevRev" + "id": "ART-4206_KNOWLEDGE_NODE-10", + "text": "|\\n| 7 | \"progress\": { |\\n| 8 | \"progress_state\": \"skill_triggered\", |\\n| 9 | \"skill_triggered\": { |\\n| 10 | \"args\": { /* skill arguments */ }, |\\n| 11 | \"skill_name\": \"SkillName\", |\\n| 12 | \"workflow\": { /* This is not populated if KnowledgeSearch skill is called */ |\\n| 13 | \"display_id\": \"workflow-84\", |\\n| 14 | \"id\": \"don:integration:dvrv-us-1:devo/xyz:workflow/84\" |\\n| 15 | } |\\n| 16 | } |\\n| 17 | }, |\\n| 18 | \"session\": \"don:core:dvrv-us-1:devo/xyz:ai_agent_session/3810\", |\\n| 19 |", + "title": "Agents async API | DevRev | Docs" }, { - "id": "ART-1950_KNOWLEDGE_NODE-25", - "text": "be recursively made of smaller parts. Events and work items must be related to parts. In general, parts are the core objects that almost all other objects are linked to, which helps enforce the notion of tying everything back to the product or service.\\n\\n\\xf0\\x9f\\x8e\\xa5 Video: Trails\\n\\n*Trails* is an extensible interface that allows you to view and manage your part hierarchy and related items. Think of it like a graph canvas that\\'s rendering linkages among items\\xe2\\x80\\x94including", - "title": "Parts & trails | Computer by DevRev | DevRev" + "id": "ART-4206_KNOWLEDGE_NODE-11", + "text": "\"session_object\": \"unique_conversation_identifier\" |\\n| 20 | }, |\\n| 21 | \"type\": \"ai_agent_response\" |\\n| 22 | } |\\n| 23 | } |\\n```\\n\\nSkill executed\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | { |\\n| 2 | \"payload\": { |\\n| 3 | \"ai_agent_response\": { |\\n| 4 | \"agent\": \"don:core:dvrv-us-1:devo/xyz:ai_agent/123\", |\\n| 5 | \"agent_response\": \"progress\", |\\n| 6 | \"client_metadata\": { /* your original metadata */ }, |\\n| 7 | \"progress\": { |\\n| 8 | \"progress_state\": \"skill_executed\", |\\n| 9 |", + "title": "Agents async API | DevRev | Docs" } ] }, @@ -1236,53 +1236,53 @@ "query": "resolution time grouped by Priority and Customer segment", "retrievals": [ { - "id": "ART-1986_KNOWLEDGE_NODE-41", - "text": "resolution is due in one day, the vista displays five minutes. In the case where the first response isn't provided within five minutes, the timer displays negative values (such as -10m), which indicates that it's been 10 minutes since the first response was due. Conversations or tickets can also be grouped by SLA stages.\\n\\nIn the **Detailed View**, all metrics applied to the ticket or conversation can be viewed along with their current stage.\\n\\nFiltering tickets by Next SLA", - "title": "Service-level agreement | Computer for Support Teams | DevRev" + "id": "ART-15716_KNOWLEDGE_NODE-36", + "text": "the Dashboards section.\\n\\nAdd a widget for \\xe2\\x80\\x9cTicket Resolution Time\\xe2\\x80\\x9d or \\xe2\\x80\\x9cAverage Time to Resolution.\\xe2\\x80\\x9d\\n\\nConfigure the widget to display data by agent, team, or time period.\\n\\nUse filters to focus on specific ticket types, priorities, or customer segments.\\n\\nFor more granular analysis, use a table or chart widget with custom SQL or filters.\\n\\nThis will help you monitor and improve your team\\xe2\\x80\\x99s responsiveness.5. Configuring branding of the", + "title": "Support queries related playbook" }, { - "id": "ART-1003_KNOWLEDGE_NODE-20", - "text": "AverageResolutionTime\\nFROM tickets t\\nWHERE t.status = 'resolved'\\nAND EXTRACT(@period FROM t.created_at) = EXTRACT(@period FROM CURRENT_DATE);\\n-- NOTE: Replace @period with 'DAY', 'WEEK', 'MONTH', or 'QUARTER'.\\n\\n\\nCustomer Satisfaction Score (CSAT)\\n\\n\\n Definition\\n \\n A metric that gauges customer satisfaction with the support provided, typically collected through surveys.\\n \\n \\n Calculation\\n \\n (Number of satisfied responses) / (Total number of responses) * 100\\n", + "id": "ART-1003_KNOWLEDGE_NODE-19", + "text": "t.created_at) = EXTRACT(@period FROM CURRENT_DATE);\\n-- NOTE: Replace @period with 'DAY', 'WEEK', 'MONTH', or 'QUARTER'.\\n\\n\\nAverage Resolution Time (ART)\\n\\n\\n Definition\\n \\n The average time it takes to resolve a customer issue from the moment it\\xe2\\x80\\x99s reported.\\n \\n \\n Calculation\\n \\n (Sum of resolution times for all resolved tickets) / (Total number of resolved tickets)\\n \\n \\n\\n\\nSELECT AVG(TIMESTAMPDIFF(MINUTE, t.created_at, t.resolved_at)) AS", "title": "Understanding a Support Lead's Pain Points and KPIs" }, { - "id": "ART-1039_KNOWLEDGE_NODE-3", - "text": "high-quality video experiences became undeniable.\\n\\nThe Challenge\\n-------------\\n\\nProviding exceptional customer support means connecting with your customers wherever they are, in real-time. As companies scale, it becomes increasingly difficult to provide the same high standard of service to a growing number of customers \\xe2\\x80\\x94 without breaking the bank. In today\\xe2\\x80\\x99s crowded marketplace where it\\xe2\\x80\\x99s possible to get a SaaS company up and running in less than a day,", - "title": "100ms delivers differentiated customer support through a unified channel" + "id": "ART-1003_KNOWLEDGE_NODE-8", + "text": "calculate these things manually\\n Make sure there is automation to keep these numbers up to date and don\\xe2\\x80\\x99t rely on a human to calculate\\n Manual/human-based calculations will always be out of date and error prone.\\n \\n \\n\\n\\nKPIs to track:\\n\\n\\n First Response Time\\n Average Resolution Time\\n Customer Satisfaction Score\\n Net Promoter Score\\n Escalation Rate\\n\\n\\nCustomer satisfaction (CSAT)\\n\\nTechnically this should be at the top of the list as this is all that", + "title": "Understanding a Support Lead's Pain Points and KPIs" }, { - "id": "ART-1039_KNOWLEDGE_NODE-15", - "text": "[SLA](/legal/sla)\\n* [DPA](/legal/dpa)\\n* [Subprocessors](/security/sub-processors)\\n* [Cookie Policy](/legal/cookie-policy)\\n* [Privacy Policy](/legal/privacy-policy)\\n* [Terms of Service](/legal/terms-of-service)\\n\\n[System Status](/status)\\n\\n\\xc2\\xa9 2025 DevRev Inc.'", - "title": "100ms delivers differentiated customer support through a unified channel" + "id": "ART-1003_KNOWLEDGE_NODE-20", + "text": "AverageResolutionTime\\nFROM tickets t\\nWHERE t.status = 'resolved'\\nAND EXTRACT(@period FROM t.created_at) = EXTRACT(@period FROM CURRENT_DATE);\\n-- NOTE: Replace @period with 'DAY', 'WEEK', 'MONTH', or 'QUARTER'.\\n\\n\\nCustomer Satisfaction Score (CSAT)\\n\\n\\n Definition\\n \\n A metric that gauges customer satisfaction with the support provided, typically collected through surveys.\\n \\n \\n Calculation\\n \\n (Number of satisfied responses) / (Total number of responses) * 100\\n", + "title": "Understanding a Support Lead's Pain Points and KPIs" }, { - "id": "ART-1986_KNOWLEDGE_NODE-39", - "text": "marked as spam | | |\\n| Next response time | | A new message on the conversation with the customer after the customer experience engineer replied | * The agent replied to the conversation * The conversation is moved to Waiting on User/Resolved * The conversation is marked as spam | | |\\n| Full resolution time | | Conversation created | * The conversation has moved to the Resolved/Archived * The conversation is marked as spam | The conversation is moved to Waiting on User | The", - "title": "Service-level agreement | Computer for Support Teams | DevRev" + "id": "ART-1004_KNOWLEDGE_NODE-7", + "text": "time it takes for a specific support engineer to resolve a customer issue from the moment it\\xe2\\x80\\x99s reported.\\n \\n \\n Calculation\\n \\n (Sum of resolution times for all resolved tickets by the engineer) / (Total number of resolved tickets by the engineer)\\n \\n \\n\\n\\nSELECT engineer_id, AVG(TIMESTAMPDIFF(MINUTE, t.created_at, t.resolved_at)) AS IndividualAverageResolutionTime\\nFROM tickets t\\nWHERE t.status = 'resolved'\\nAND EXTRACT(@period FROM t.created_at) =", + "title": "Understanding a Support Engineer's Pain Points and KPIs" }, { - "id": "ART-1039_KNOWLEDGE_NODE-5", - "text": "problem was interacting with our customers and really understanding the urgency of every conversation. We had over 300 Slack Connect channels for our users. The conversations could go from design discussions to finding bugs to architecture, and there was no way to delineate these conversations from ones where a customer is saying, \\xe2\\x80\\x98I\\xe2\\x80\\x99m having an outage right now. I need urgent help\\xe2\\x80\\x9d.\\n\\nManaging and prioritizing customer conversations and requests in Slack was a", - "title": "100ms delivers differentiated customer support through a unified channel" + "id": "ART-1974_KNOWLEDGE_NODE-25", + "text": "lower priority than existing customer orgs.\\n\\n**Tags** [*values*]\\n\\n* Stalled\\n* Priority/Escalated\\n* Fast/Slow Moving\\n* Blocked\\n* Resolution: [*value*]\\n\\nStages\\n------\\n\\nThe following figure shows the state machine for conversations.\\n\\n```\\nClosed\\n\\n\\n\\nIn progress\\n\\n\\n\\nOpen\\n\\n\\n\\nValid\\n\\n\\n\\nSpam\\n\\n\\n\\nReview\\n\\n\\n\\nWaiting on user\\n\\n\\n\\nUser responds\\n\\n\\n\\nHold for Dependency\\n\\n\\n\\nDependency Solved\\n\\n\\n\\nSupport", + "title": "Conversations | Computer for Support Teams | DevRev" }, { - "id": "ART-2133_KNOWLEDGE_NODE-21", - "text": "customer at a much deeper level.\\n\\nTime Travel Establishing the history of a customer \\xe2\\x80\\x93 events, changes to records, versions, time logs\\xe2\\x80\\xa6 essentially traveling back in time \\xe2\\x80\\x93 is one of the hardest things in customer relationship management. Support, product management, and other business-to-business conversations\\n\\nPage 7 of 16\\n\\nThe Essential Methodology\\n\\nLess But Better\\n\\nare otherwise mostly point-in- time, with a lot of recency bias that results in", - "title": "The Essential Methodology: Less but Better" + "id": "ART-1968_KNOWLEDGE_NODE-25", + "text": "insights\\n=====================\\n\\n* **Resolution rate**\\n\\n The percentage of conversations resolved.\\n* **SLA compliance rate**\\n\\n The percentage of conversations where the SLA was met out of all conversations where the SLA was applied.\\n* **Average CSAT score**\\n\\n The average customer satisfaction score for conversations.\\n* **Average first response time**\\n\\n The average time for the first response to customer conversations.\\n\\nCustomer & product impact\\n-------------------------\\n\\n*", + "title": "Conversation insights | Support analytics | Computer for Support Teams | DevRev" }, { - "id": "ART-1003_KNOWLEDGE_NODE-19", - "text": "t.created_at) = EXTRACT(@period FROM CURRENT_DATE);\\n-- NOTE: Replace @period with 'DAY', 'WEEK', 'MONTH', or 'QUARTER'.\\n\\n\\nAverage Resolution Time (ART)\\n\\n\\n Definition\\n \\n The average time it takes to resolve a customer issue from the moment it\\xe2\\x80\\x99s reported.\\n \\n \\n Calculation\\n \\n (Sum of resolution times for all resolved tickets) / (Total number of resolved tickets)\\n \\n \\n\\n\\nSELECT AVG(TIMESTAMPDIFF(MINUTE, t.created_at, t.resolved_at)) AS", - "title": "Understanding a Support Lead's Pain Points and KPIs" + "id": "ART-1899_KNOWLEDGE_NODE-1", + "text": "resolution time by 64%, improved first response time by over 83%, and increased their customer satisfaction score by 30%. They also saw a 20% increase in conversion rates.\\n\\nWith DevRev, Tough Trucks for Kids can now provide top-notch, scalable customer support. They're set up to maintain high customer delight as they continue to grow.\\n\\nCase Study: Link\"", + "title": "Tough Trucks for Kids Story" }, { - "id": "ART-970_KNOWLEDGE_NODE-47", - "text": "customers, including their support interactions, engagements, and product usage.\\n Consider the possibilities of identifying and prioritizing high-impact items based on their revenue implications.\\n\\n\\nSupport Engineer:\\n\\n\\n How would your approach change if you knew about potential opportunities or deals with the customer?\\n Imagine not having to engage in the tedious task of copying and pasting between engineering issues and your tickets.\\n What if you could effortlessly track the status", - "title": "The Story" + "id": "ART-4181_KNOWLEDGE_NODE-10", + "text": "goals\\n\\nChoose from pre-built metrics such as response time and resolution time, or tailor metrics to your requirements\\n\\n![]()\\n\\nEffortlessly assign SLAs\\n========================\\n\\nPowered by intelligent automation and flexible customization to ensure customers consistently receive the right level of support\\n================================================================================================================================\\n\\n[Try for free](/request-a-demo)\\n\\nAutomated SLA", + "title": "Support like a lightning fast pit-crew" }, { - "id": "ART-1004_KNOWLEDGE_NODE-7", - "text": "time it takes for a specific support engineer to resolve a customer issue from the moment it\\xe2\\x80\\x99s reported.\\n \\n \\n Calculation\\n \\n (Sum of resolution times for all resolved tickets by the engineer) / (Total number of resolved tickets by the engineer)\\n \\n \\n\\n\\nSELECT engineer_id, AVG(TIMESTAMPDIFF(MINUTE, t.created_at, t.resolved_at)) AS IndividualAverageResolutionTime\\nFROM tickets t\\nWHERE t.status = 'resolved'\\nAND EXTRACT(@period FROM t.created_at) =", + "id": "ART-1004_KNOWLEDGE_NODE-3", + "text": "to deliver good results quickly.\\n\\nKPIs to track:\\n\\n\\n Individual First Response Time\\n Individual Average Resolution Time\\n Ticket Volume\\n\\n\\nRepetitive tasks\\n\\nAll customers are different, but not all problems or process steps are. One of the most frustrating things in this position is dealing with the repetitive grunt work (I refer to this as \\xe2\\x80\\x9cwork suck\\xe2\\x80\\x9d) and the potential monotony of tasks. HINT: automation and/or intelligent systems are key here!\\n\\nTo make", "title": "Understanding a Support Engineer's Pain Points and KPIs" } ] @@ -1292,54 +1292,54 @@ "query": "add attributes in MSAT snap-in", "retrievals": [ { - "id": "ART-1846_KNOWLEDGE_NODE-8", - "text": "example of a snap-kit JSON:\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | { |\\n| 2 | \"snap_kit_body\": { |\\n| 3 | \"body\": { |\\n| 4 | \"snaps\": [ |\\n| 5 | { |\\n| 6 | \"elements\": [ |\\n| 7 | { |\\n| 8 | \"action_id\": \"user_snap_kit_action\", |\\n| 9 | \"action_type\": \"remote\", |\\n| 10 | \"elements\": [ |\\n| 11 | { |\\n| 12 | \"element\": { |\\n| 13 | \"action_id\": \"select\", |\\n| 14 | \"action_type\": \"client\", |\\n| 15 | \"initial_selected_option\": { |\\n| 16 | \"text\": { |\\n| 17 | \"text\": \"Ticket\", |\\n| 18 | \"type\":", - "title": "Customizing snap-in configuration | DevRev | Docs" + "id": "ART-1619_KNOWLEDGE_NODE-1", + "text": "|\\n| > | -H \"Authorization: Bearer \" \\\\ |\\n| > | -H \"Content-Type: application/json\" \\\\ |\\n| > | -d \\'{ |\\n| > | \"id\": \"string\", |\\n| > | \"user\": \"string\" |\\n| > | }\\' |\\n```\\n\\n[Try it](/beta/api-reference/snap-ins/resources-post?explorer=true)\\n\\n200Successful\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | { |\\n| 2 | \"snap_in_version\": { |\\n| 3 | \"id\": \"string\", |\\n| 4 | \"display_id\": \"string\" |\\n| 5 | }, |\\n| 6 | \"event_sources\": {}, |\\n| 7 | \"inputs\": {}, |\\n| 8 | \"keyrings\": {} |\\n| 9 | }", + "title": "Resources Snap Ins (POST) | DevRev | Docs" }, { - "id": "ART-1278_KNOWLEDGE_NODE-6", - "text": "discussion tab of the specified Product\\nsection. The configuration for this action can be customized through the input\\nparameters of the snap-in.\\n\\n[2](/snapin-development/tutorials/triggered-external-source#creating-the-snap-in)\\n\\n### Creating the snap-in\\n\\n#### Updating the manifest\\n\\nTo outline the structure of the snap-in, the initial step is to define key\\nattributes in the snap-in\\xe2\\x80\\x99s manifest. Begin by specifying the name, description,\\nand account display name for the", - "title": "Snap-in triggered by an external source | DevRev | Docs" + "id": "ART-2028_KNOWLEDGE_NODE-24", + "text": "[Snap-ins](/docs/snapins)\\n[Automate](/docs/automate)\\n[Work duration](/docs/automations/work-duration)\\n\\nWork duration\\n=============\\n\\n[Work duration](/marketplace/work-duration) offers the ability\\nto track how much work issues and tickets took to complete, measured by time\\nspent in work sessions.\\n\\nThe snap-in adds a new attribute to tickets and issues which automatically\\ncalculates the work duration for that item. Work duration is meassured in time\\nspent through work sessions. A work", + "title": "Work duration | Automate | Snap-ins | DevRev" }, { - "id": "ART-1846_KNOWLEDGE_NODE-19", - "text": "change in future updates.\\n\\nFor more details on the snap-kit JSON format and available elements, refer to the [DevRev Snap-kit documentation](/snapin-development/references/snapkit).\\n\\nWas this page helpful?\\n\\nYesNo\\n\\n[Previous](/snapin-development/references/snap-in-resources)[#### Development best practices\\n\\nNext](/snapin-development/best-practices)[Built with](https://buildwithfern.com/?utm_campaign=buildWith&utm_medium=docs&utm_source=developer.devrev.ai)'", - "title": "Customizing snap-in configuration | DevRev | Docs" + "id": "ART-1545_KNOWLEDGE_NODE-442", + "text": "object.\\nsnap_in_version object\\nShow 2 properties\\nevent_sources map from strings to strings Optional\\n\\nThe event sources for the snap-in.\\n\\ninputs map from strings to any Optional\\n\\nThe inputs for the snap-in.\\n\\nkeyrings map from strings to objects Optional\\n\\nMap of keyring names and its data.\\n\\nShow 2 properties\\nAPI Reference snap-ins Update.\\n\\nPOST https://api.devrev.ai / snap-ins.update\\n\\nUpdates a snap-in.\\n\\nRequest.\\n\\nThis endpoint expects an object.\\nid string Required\\n\\nThe", + "title": "Create (Beta) \u2014 DevRev | Docs" }, { - "id": "ART-1847_KNOWLEDGE_NODE-9", - "text": "JSON:\\n\\n[code]\\n\\n 1| { \\n ---|--- \\n 2| \"snap_kit_body\": { \\n 3| \"body\": { \\n 4| \"snaps\": [ \\n 5| { \\n 6| \"elements\": [ \\n 7| { \\n 8| \"action_id\": \"user_snap_kit_action\", \\n 9| \"action_type\": \"remote\", \\n 10| \"elements\": [ \\n 11| { \\n 12| \"element\": { \\n 13| \"action_id\": \"select\", \\n 14|", - "title": "Customizing snap-in configuration \u2014 DevRev | Docs" + "id": "ART-1566_KNOWLEDGE_NODE-444", + "text": "object.\\nsnap_in_version object\\nShow 2 properties\\nevent_sources map from strings to strings Optional\\n\\nThe event sources for the snap-in.\\n\\ninputs map from strings to any Optional\\n\\nThe inputs for the snap-in.\\n\\nkeyrings map from strings to objects Optional\\n\\nMap of keyring names and its data.\\n\\nShow 2 properties\\nAPI Reference snap-ins Update.\\n\\nPOST https://api.devrev.ai / snap-ins.update\\n\\nUpdates a snap-in.\\n\\nRequest.\\n\\nThis endpoint expects an object.\\nid string Required\\n\\nThe", + "title": "Transition (Beta) \u2014 DevRev | Docs" }, { - "id": "ART-1473_KNOWLEDGE_NODE-9", - "text": "displaying them on the discussion tab of the specified Product section. The configuration for this action can be customized through the input parameters of the snap-in.\\n\\n[2](/public/snapin-development/tutorials/triggered-external-source#creating-the-snap-in)\\n\\n### Creating the snap-in\\n\\n#### Updating the manifest\\n\\nTo outline the structure of the snap-in, the initial step is to define key attributes in the snap-in\\xe2\\x80\\x99s manifest. Begin by specifying the name, description, and", - "title": "Snap-in triggered by an external source \u2014 DevRev | Docs" + "id": "ART-1290_KNOWLEDGE_NODE-9", + "text": "is the base type that all other snaps inherit from.\\n\\n*Properties*\\n\\n* `type` (required): Type of snap.\\n* `block_id` (optional): A unique identifier for the snap. If not provided, a random ID is generated.\\n\\n###### Action\\n\\nBase interface for action components.\\n\\n*Action types*\\n\\n* **Remote action**: It triggers a backend API and is handled by the backend.\\n* **Client action**: It triggers a client-side action and is handled by the client.\\n\\n*Properties*\\n\\n* `action_id` (required): An", + "title": "Snapkit | DevRev | Docs" }, { - "id": "ART-1846_KNOWLEDGE_NODE-1", - "text": "(beta)](/snapin-development/references/customizing-snap-in-configuration#update-snap-in-inputs-beta)\\n* [Request payload](/snapin-development/references/customizing-snap-in-configuration#request-payload)\\n* [Response](/snapin-development/references/customizing-snap-in-configuration#response)\\n* [Success response](/snapin-development/references/customizing-snap-in-configuration#success-response)\\n* [Error", - "title": "Customizing snap-in configuration | DevRev | Docs" + "id": "ART-1290_KNOWLEDGE_NODE-192", + "text": "customize the options, initial selections, and other values according to your requirements.\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | { |\\n| 2 | \"object\": \"source_id\", |\\n| 3 | \"body\": \"Giphy\", |\\n| 4 | \"type\": \"timeline_comment\", |\\n| 5 | \"snap_kit_body\": { |\\n| 6 | \"snap_in_id\": \"snap_in_id\", |\\n| 7 | \"snap_in_action_name\": \"giphy\", |\\n| 8 | \"body\": { |\\n| 9 | \"snaps\": [ |\\n| 10 | { |\\n| 11 | \"type\": \"card\", |\\n| 12 | \"title\": { |\\n| 13 | \"text\": \"Hip hip hurray!\", |\\n| 14 | \"type\": \"plain_text\"", + "title": "Snapkit | DevRev | Docs" }, { - "id": "ART-1276_KNOWLEDGE_NODE-6", - "text": "manifest\\n\\nTo outline the structure of the snap-in, the initial step is to define key attributes in the snap-in\\xe2\\x80\\x99s manifest. Begin by specifying the name, description, and account display name for the snap-in.\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | version: \"2\" |\\n| 2 | name: \"GitHub issue creator\" |\\n| 3 | description: \"Replicate DevRev issues in GitHub.\" |\\n| 4 | |\\n| 5 | service_account: |\\n| 6 | display_name: GitHub Issue Creator", - "title": "Using a snap-in to perform an external action | DevRev | Docs" + "id": "ART-1543_KNOWLEDGE_NODE-440", + "text": "returns an object.\\nsnap_in_version object\\nShow 2 properties\\nevent_sources map from strings to strings Optional\\n\\nThe event sources for the snap-in.\\n\\ninputs map from strings to any Optional\\n\\nThe inputs for the snap-in.\\n\\nkeyrings map from strings to objects Optional\\n\\nMap of keyring names and its data.\\n\\nShow 2 properties\\nAPI Reference snap-ins Resources Post.\\n\\nPOST https://api.devrev.ai / snap-ins.resources\\n\\nGets snap-in resources for a user in a snap-in.\\n\\nRequest.\\n\\nThis", + "title": "Metric Definitions List Post (Beta) \u2014 DevRev | Docs" }, { - "id": "ART-1472_KNOWLEDGE_NODE-10", - "text": "outline the structure of the snap-in, the initial step is to define key attributes in the snap-in\\xe2\\x80\\x99s manifest. Begin by specifying the name, description, and account display name for the snap-in.\\n\\n[code]\\n\\n 1| version: \"2\" \\n ---|--- \\n 2| name: \"GitHub issue creator\" \\n 3| description: \"Replicate DevRev issues in GitHub.\" \\n 4| \\n 5| service_account: \\n 6| display_name: GitHub Issue Creator\\n[/code] \\n", - "title": "Using a snap-in to perform an external action \u2014 DevRev | Docs" + "id": "ART-1562_KNOWLEDGE_NODE-442", + "text": "returns an object.\\nsnap_in_version object\\nShow 2 properties\\nevent_sources map from strings to strings Optional\\n\\nThe event sources for the snap-in.\\n\\ninputs map from strings to any Optional\\n\\nThe inputs for the snap-in.\\n\\nkeyrings map from strings to objects Optional\\n\\nMap of keyring names and its data.\\n\\nShow 2 properties\\nAPI Reference snap-ins Resources Post.\\n\\nPOST https://api.devrev.ai / snap-ins.resources\\n\\nGets snap-in resources for a user in a snap-in.\\n\\nRequest.\\n\\nThis", + "title": "Get (Beta) \u2014 DevRev | Docs" }, { - "id": "ART-1847_KNOWLEDGE_NODE-2", - "text": "(beta)](/public/snapin-development/references/customizing-snap-in-configuration#update-snap-in-inputs-beta)\\n * [Request payload](/public/snapin-development/references/customizing-snap-in-configuration#request-payload)\\n * [Response](/public/snapin-development/references/customizing-snap-in-configuration#response)\\n * [Success response](/public/snapin-development/references/customizing-snap-in-configuration#success-response)\\n * [Error", - "title": "Customizing snap-in configuration \u2014 DevRev | Docs" + "id": "ART-1564_KNOWLEDGE_NODE-441", + "text": "returns an object.\\nsnap_in_version object\\nShow 2 properties\\nevent_sources map from strings to strings Optional\\n\\nThe event sources for the snap-in.\\n\\ninputs map from strings to any Optional\\n\\nThe inputs for the snap-in.\\n\\nkeyrings map from strings to objects Optional\\n\\nMap of keyring names and its data.\\n\\nShow 2 properties\\nAPI Reference snap-ins Resources Post.\\n\\nPOST https://api.devrev.ai / snap-ins.resources\\n\\nGets snap-in resources for a user in a snap-in.\\n\\nRequest.\\n\\nThis", + "title": "List (Beta) \u2014 DevRev | Docs" }, { - "id": "ART-1296_KNOWLEDGE_NODE-9", - "text": "changed. Any existing function can be removed. A new function can be added. |\\n| Commands | For existing commands: - All properties can be changed. Any existing command can be removed. A new command can be added. |\\n| Snap-kit actions | For existing snap-kit-actions: - The description can be changed. - The function can be changed. Any existing snap-kit-action can be removed. A new snap-kit-action can be added. |\\n| Service account | The display name of the service", - "title": "Upgrade snap-ins | DevRev | Docs" + "id": "ART-1543_KNOWLEDGE_NODE-442", + "text": "data.\\n\\nShow 2 properties\\nAPI Reference snap-ins Update.\\n\\nPOST https://api.devrev.ai / snap-ins.update\\n\\nUpdates a snap-in.\\n\\nRequest.\\n\\nThis endpoint expects an object.\\nid string Required\\n\\nThe ID of the snap-in to update.\\n\\ninputs_values map from strings to any Optional\\n\\nThe updated values of the inputs.\\n\\nResponse.\\n\\nThis endpoint returns an object.\\nsnap_in object\\nShow 7 properties\\nAPI Reference snap-widgets Create.\\n\\nPOST https://api.devrev.ai /", + "title": "Metric Definitions List Post (Beta) \u2014 DevRev | Docs" } ] }, @@ -1348,54 +1348,54 @@ "query": "Slack bot not working after multiple test tickets", "retrievals": [ { - "id": "ART-4021_KNOWLEDGE_NODE-5", - "text": "ticket conversion](/docs/product/conversation-ticket)\\n + [Tickets](/docs/product/tickets)\\n + [Routing](/docs/product/routing)\\n + [Support best practices](/docs/product/support-bp)\\n + [Customer portal](/docs/product/support-portal)\\n + [Questions & answers](/docs/product/qa)\\n + [Knowledge Base](/docs/product/knowledge-base)\\n\\n - [Articles](/docs/product/articles)\\n - [Collections](/docs/product/collection)\\n + [Turing AI agent](/docs/product/conversational-bot)\\n\\n - [Best", - "title": "Slack scraper | Automate | Snap-ins | DevRev" - }, - { - "id": "ART-12395_KNOWLEDGE_NODE-5", - "text": "ticket conversion](/docs/product/conversation-ticket)\\n + [Tickets](/docs/product/tickets)\\n + [Routing](/docs/product/routing)\\n + [Support best practices](/docs/product/support-bp)\\n + [Customer portal](/docs/product/support-portal)\\n + [Questions & answers](/docs/product/qa)\\n + [Knowledge Base](/docs/product/knowledge-base)\\n\\n - [Articles](/docs/product/articles)\\n - [Collections](/docs/product/collection)\\n + [Turing AI agent](/docs/product/conversational-bot)\\n\\n - [Best", - "title": "Slack Broadcaster | Automate | Snap-ins | DevRev" + "id": "ART-2017_KNOWLEDGE_NODE-25", + "text": "ticket\\'s owner and subscribers, when a ticket\\'s resolution time SLA changes into the *Warning* or *Breached* stage.\\n\\n![]()\\n\\nFor more information, refer to the\\n[SLA status change Slack notifier snap-in](/marketplace/sla-status-change-slack-notifier) on the DevRev\\nmarketplace.\\n\\nInstallation\\n------------\\n\\n1. Create a Slack app for your workspace in .\\n2. In App features, generate bot token in **OAuth & Permissions**.\\n3. Grant the app bot the following", + "title": "SLA status change Slack notifier | Automate | Snap-ins | DevRev" }, { - "id": "ART-4199_KNOWLEDGE_NODE-5", - "text": "ticket conversion](/docs/product/conversation-ticket)\\n + [Tickets](/docs/product/tickets)\\n + [Routing](/docs/product/routing)\\n + [Support best practices](/docs/product/support-bp)\\n + [Customer portal](/docs/product/support-portal)\\n + [Questions & answers](/docs/product/qa)\\n + [Knowledge Base](/docs/product/knowledge-base)\\n\\n - [Articles](/docs/product/articles)\\n - [Collections](/docs/product/collection)\\n + [Turing AI agent](/docs/product/conversational-bot)\\n\\n - [Best", + "id": "ART-4199_KNOWLEDGE_NODE-28", + "text": "**Trigger URL** that is displayed.\\n6. Paste the Trigger URL under **Enable Events** in the custom Slack bot.\\n\\n[PreviousTicket linked issues comment sync](/docs/automations/ticket-linked-issues-comment-sync)[NextIntegrate](/docs/integrate)\\n\\n#### On this page\\n\\n* [Install](#install)\\n* [Configure the custom Slack bot](#configure-the-custom-slack-bot)\\n* [Configure DevRev](#configure-devrev)\\n\\n[Enterprise grade security to protect customer data\\n\\nLearn more about", "title": "Slack message agent | Automate | Snap-ins | DevRev" }, { - "id": "ART-4199_KNOWLEDGE_NODE-28", - "text": "**Trigger URL** that is displayed.\\n6. Paste the Trigger URL under **Enable Events** in the custom Slack bot.\\n\\n[PreviousTicket linked issues comment sync](/docs/automations/ticket-linked-issues-comment-sync)[NextIntegrate](/docs/integrate)\\n\\n#### On this page\\n\\n* [Install](#install)\\n* [Configure the custom Slack bot](#configure-the-custom-slack-bot)\\n* [Configure DevRev](#configure-devrev)\\n\\n[Enterprise grade security to protect customer data\\n\\nLearn more about", + "id": "ART-4199_KNOWLEDGE_NODE-27", + "text": "message.channels.\\n7. Add this custom app and the **DevRev Slack Bot** into the Slack channel from which you want to create the DevRev object.\\n\\nConfigure DevRev\\n----------------\\n\\n1. Add the Slack Signing Secret and Slack Bot Token copied from the custom Slack bot app.\\n2. Add the channel IDs for either incidents, tickets or issues.\\n3. Click the respective buttons to enable the sync between threads.\\n4. Select the part ID to associate a particular part.\\n5. Click **Save** and copy the", "title": "Slack message agent | Automate | Snap-ins | DevRev" }, { - "id": "ART-2035_KNOWLEDGE_NODE-5", - "text": "ticket conversion](/docs/product/conversation-ticket)\\n + [Tickets](/docs/product/tickets)\\n + [Routing](/docs/product/routing)\\n + [Support best practices](/docs/product/support-bp)\\n + [Customer portal](/docs/product/support-portal)\\n + [Questions & answers](/docs/product/qa)\\n + [Knowledge Base](/docs/product/knowledge-base)\\n\\n - [Articles](/docs/product/articles)\\n - [Collections](/docs/product/collection)\\n + [Turing AI agent](/docs/product/conversational-bot)\\n\\n - [Best", + "id": "ART-2035_KNOWLEDGE_NODE-43", + "text": "update** snap-in configuration.\\n* Applies only to tickets syncing with Slack threads.\\n* If enabled, the Slack snap-in will send notifications to the syncing thread whenever the ticket state changes.\\n\\n### Ticket digest\\n\\nTo see all open and in-progress tickets in Slack, use the /devrev ticket-digest command. This opens a modal with a paginated list of all open and in-progress tickets.\\n\\nDevRev Issues and Slack\\n-----------------------\\n\\nThe Slack snap-in allows issues to be created", "title": "Slack | Integrate | Snap-ins | DevRev" }, { - "id": "ART-12395_KNOWLEDGE_NODE-13", - "text": "group](/docs/automations/set-user-preference)\\n - [SLA status change Slack notifier](/docs/automations/sla-change-notifier)\\n - [Slash commands](/docs/automations/slash-commands)\\n - [Spam Shield](/docs/automations/spam-shield)\\n - [Subtype Migration](/docs/automations/subtype-migration)\\n - [Ticket age in engineering](/docs/automations/ticket-age-in-engineering)\\n - [Ticket issue field migrator](/docs/automations/ticket-issue-field-migrator)\\n - [Ticket", - "title": "Slack Broadcaster | Automate | Snap-ins | DevRev" + "id": "ART-968_KNOWLEDGE_NODE-1", + "text": "stays in Slack and doesn\\xe2\\x80\\x99t extend to DevRev tickets.\\n\\n\\xe2\\x97\\x8f Solution:\\nDeveloped by: Hariharan\\nStatus: Tested and verified.\\nCustomer Approval: Approved\\n\\xe2\\x97\\x8b Brief:\\nCustom Snap-in connected with a custom Slack application that would automatically tag\\nthe on-call members upon ticket creation at Slack.\\n\\n\\xe2\\x97\\x8b Description:\\nA custom application in Slack marketplace is to be created which would perform the\\ntagging by referencing the group members in Slack.", + "title": "Rocketium: On call Tagging - Slack" }, { - "id": "ART-12395_KNOWLEDGE_NODE-14", - "text": "Immutability](/docs/automations/ticket-immutability)\\n - [Ticket email notifier](/docs/automations/ticket-email-notifier)\\n - [Task tracker](/docs/automations/task-tracker)\\n - [Ticket Tagger](/docs/automations/ticket-tagger)\\n - [Tracxn sync](/docs/automations/tracxn-sync)\\n - [User group validator](/docs/automations/user-group-validator)\\n - [Work duration](/docs/automations/work-duration)\\n - [Operational SLA Metrics](/docs/automations/operational-sla-metrics)\\n -", - "title": "Slack Broadcaster | Automate | Snap-ins | DevRev" + "id": "ART-3235_KNOWLEDGE_NODE-26", + "text": "system.\\n\\nAfter configuring these settings, the snap-in automatically processes new tickets and enriches their **Reported By** fields based on the provided email addresses.\\n\\n[PreviousSlack Broadcaster](/docs/automations/slack-broadcaster)[NextTicket approval workflow](/docs/automations/ticket-approval-workflow)\\n\\n#### On this page\\n\\n* [Installation](#installation)\\n* [Configuration](#configuration)\\n\\n[Enterprise grade security to protect customer data\\n\\nLearn more about", + "title": "Reported by enricher | Automate | Snap-ins | DevRev" }, { - "id": "ART-4199_KNOWLEDGE_NODE-14", - "text": "Immutability](/docs/automations/ticket-immutability)\\n - [Ticket email notifier](/docs/automations/ticket-email-notifier)\\n - [Task tracker](/docs/automations/task-tracker)\\n - [Ticket Tagger](/docs/automations/ticket-tagger)\\n - [Tracxn sync](/docs/automations/tracxn-sync)\\n - [User group validator](/docs/automations/user-group-validator)\\n - [Work duration](/docs/automations/work-duration)\\n - [Operational SLA Metrics](/docs/automations/operational-sla-metrics)\\n -", - "title": "Slack message agent | Automate | Snap-ins | DevRev" + "id": "ART-2035_KNOWLEDGE_NODE-38", + "text": "recommended if you already have a conversation in progress. Configure the snap-in to send or not send a ticket summary card to the Slack thread using the **Notify on conversation to ticket conversion** setting. Regardless, the Slack thread will sync with the new ticket instead of the ongoing conversation.\\n\\n![]()\\n\\nSlack does not support slash commands in threads.\\n\\nChoosing one of the first two options will open a pop-up modal with the new ticket form. Complete the required fields; some", + "title": "Slack | Integrate | Snap-ins | DevRev" }, { - "id": "ART-4199_KNOWLEDGE_NODE-13", - "text": "group](/docs/automations/set-user-preference)\\n - [SLA status change Slack notifier](/docs/automations/sla-change-notifier)\\n - [Slash commands](/docs/automations/slash-commands)\\n - [Spam Shield](/docs/automations/spam-shield)\\n - [Subtype Migration](/docs/automations/subtype-migration)\\n - [Ticket age in engineering](/docs/automations/ticket-age-in-engineering)\\n - [Ticket issue field migrator](/docs/automations/ticket-issue-field-migrator)\\n - [Ticket", - "title": "Slack message agent | Automate | Snap-ins | DevRev" + "id": "ART-2035_KNOWLEDGE_NODE-36", + "text": "Slack Channel ID in the **Channel ID to send conversation notifications** snap-in configuration as the target to post notifications.\\n\\n* Any new message within tickets in the customer messages panel is also subjected to the same automation.\\n* To prevent notification overload, each conversation or ticket is subject to a five minute cooldown period between notifications. Multiple consecutive messages within this window will not trigger additional notifications.\\n* Notification threads are not", + "title": "Slack | Integrate | Snap-ins | DevRev" + }, + { + "id": "ART-2036_KNOWLEDGE_NODE-15", + "text": "[Custom field migration](/docs/automations/custom-field-migration)\\n - [Slack scraper](/docs/automations/slack-scraper)\\n - [Slack Broadcaster](/docs/automations/slack-broadcaster)\\n - [Reported by enricher](/docs/automations/ticket-reported-by)\\n - [Ticket approval workflow](/docs/automations/ticket-approval-workflow)\\n - [Ticket linked issues comment sync](/docs/automations/ticket-linked-issues-comment-sync)\\n - [Slack message agent](/docs/automations/slack-message-agent)\\n", + "title": "SendSafely | Integrate | Snap-ins | DevRev" }, { - "id": "ART-4021_KNOWLEDGE_NODE-13", - "text": "group](/docs/automations/set-user-preference)\\n - [SLA status change Slack notifier](/docs/automations/sla-change-notifier)\\n - [Slash commands](/docs/automations/slash-commands)\\n - [Spam Shield](/docs/automations/spam-shield)\\n - [Subtype Migration](/docs/automations/subtype-migration)\\n - [Ticket age in engineering](/docs/automations/ticket-age-in-engineering)\\n - [Ticket issue field migrator](/docs/automations/ticket-issue-field-migrator)\\n - [Ticket", - "title": "Slack scraper | Automate | Snap-ins | DevRev" + "id": "ART-2017_KNOWLEDGE_NODE-27", + "text": "Connection**.\\n * Select **Slack** from the dowpdown list.\\n * Give it a name and sign in with Slack. Ensure to toggle on **Make public** to make the connection public for your organization.\\n\\nConfigure the snap-in\\n---------------------\\n\\n1. In the **Configuration** tab, the first input field to set is *filters*. Here you can declare for which tickets to track the SLA status and to which channels to send notifications.\\n\\n Set the ticket subtype, severity, and part; the support heads", + "title": "SLA status change Slack notifier | Automate | Snap-ins | DevRev" } ] }, @@ -1404,19 +1404,24 @@ "query": "customizar severity de los tickets", "retrievals": [ { - "id": "ART-1551_KNOWLEDGE_NODE-506", + "id": "ART-996_KNOWLEDGE_NODE-14", + "text": "api_visibility: public\\n api_required: true\\n summary: true # NOTE: `title` included in summary\\n---\\n- name: severity\\n devrev_field_type: legacy_enum\\n devrev_enum:\\n - blocker\\n - high\\n - medium\\n - low\\n is_required: true\\n description: Severity of the ticket\\n gateway:\\n api_visibility: public\\n is_filterable: true\\n summary: true # NOTE: `severity` included in summary\\n\\n\\nDon\\xe2\\x80\\x99t\\nDon\\xe2\\x80\\x99t set all fields to summary: true\\n\\n - name:", + "title": "An Example Object Model Style Guide (our actual style guide)" + }, + { + "id": "ART-1564_KNOWLEDGE_NODE-506", "text": "organizations.\\n\\nticket.severity enum Optional\\n\\nFilters for tickets with any of the provided severities.\\n\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\n\\nFilters for records with any of the provided SLA stages.\\n\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\n\\nFilters for tickets with any of the provided source channels.\\n\\nticket.subtype string Optional\\n\\nFilters for tickets with any of the provided", - "title": "Update (Beta) \u2014 DevRev | Docs" + "title": "List (Beta) \u2014 DevRev | Docs" }, { - "id": "ART-1834_KNOWLEDGE_NODE-447", - "text": "organizations.\\nticket.severity enum Optional\\nFilters for tickets with any of the provided severities.\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\nFilters for records with any of the provided SLA stages.\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\nFilters for tickets with any of the provided source channels.\\nticket.subtype string Optional\\nFilters for tickets with any of the provided subtypes.\\ntype", - "title": "Delete \u2014 DevRev | Docs" + "id": "ART-1639_KNOWLEDGE_NODE-458", + "text": "for tickets that are associated with any of the provided Rev organizations.\\nticket.severity enum Optional\\nFilters for tickets with any of the provided severities.\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\nFilters for records with any of the provided SLA stages.\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\nFilters for tickets with any of the provided source channels.\\nticket.subtype string", + "title": "Export Post \u2014 DevRev | Docs" }, { - "id": "ART-1651_KNOWLEDGE_NODE-455", - "text": "the provided severities.\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\nFilters for records with any of the provided SLA stages.\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\nFilters for tickets with any of the provided source channels.\\nticket.subtype string Optional\\nFilters for tickets with any of the provided subtypes.\\ntype enum Optional\\nFilters for work of the provided types.\\nAllowed values: issue", - "title": "Create \u2014 DevRev | Docs" + "id": "ART-1244_KNOWLEDGE_NODE-23", + "text": "severities.\\n\\nAllowed values:blockerhighlowmedium\\n\\nticket.sla\\\\_summary.stagelist of enumsOptional\\n\\nFilters for records with any of the provided SLA stages.\\n\\nAllowed values:breachedcompletedpausedrunningwarning\\n\\nticket.source\\\\_channellist of stringsOptional\\n\\nFilters for tickets with any of the provided source channels.\\n\\nticket.source\\\\_channel\\\\_v2list of stringsOptional\\n\\nFilters for tickets that are associated with any of the source\\nchannels.\\n\\ntypelist of", + "title": "Export Works | DevRev | Docs" }, { "id": "ART-1979_KNOWLEDGE_NODE-29", @@ -1424,34 +1429,29 @@ "title": "Tickets | Computer for Support Teams | DevRev" }, { - "id": "ART-1633_KNOWLEDGE_NODE-454", - "text": "the provided severities.\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\nFilters for records with any of the provided SLA stages.\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\nFilters for tickets with any of the provided source channels.\\nticket.subtype string Optional\\nFilters for tickets with any of the provided subtypes.\\ntype enum Optional\\nFilters for work of the provided types.\\nAllowed values: issue", - "title": "List \u2014 DevRev | Docs" - }, - { - "id": "ART-1654_KNOWLEDGE_NODE-466", - "text": "the provided severities.\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\nFilters for records with any of the provided SLA stages.\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\nFilters for tickets with any of the provided source channels.\\nticket.subtype string Optional\\nFilters for tickets with any of the provided subtypes.\\ntype enum Optional\\nFilters for work of the provided types.\\nAllowed values: issue", - "title": "List \u2014 DevRev | Docs" + "id": "ART-1558_KNOWLEDGE_NODE-518", + "text": "response.\\n\\nticket.rev_org string Optional\\n\\nFilters for tickets that are associated with any of the provided Rev organizations.\\n\\nticket.severity enum Optional\\n\\nFilters for tickets with any of the provided severities.\\n\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\n\\nFilters for records with any of the provided SLA stages.\\n\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\n\\nFilters for tickets with any", + "title": "Metric Definitions List (Beta) \u2014 DevRev | Docs" }, { - "id": "ART-1651_KNOWLEDGE_NODE-468", - "text": "Optional\\nFilters for tickets with any of the provided severities.\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\nFilters for records with any of the provided SLA stages.\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\nFilters for tickets with any of the provided source channels.\\nticket.subtype string Optional\\nFilters for tickets with any of the provided subtypes.\\ntype enum Optional\\nFilters for work of the", - "title": "Create \u2014 DevRev | Docs" + "id": "ART-1566_KNOWLEDGE_NODE-521", + "text": "response.\\n\\nticket.rev_org string Optional\\n\\nFilters for tickets that are associated with any of the provided Rev organizations.\\n\\nticket.severity enum Optional\\n\\nFilters for tickets with any of the provided severities.\\n\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\n\\nFilters for records with any of the provided SLA stages.\\n\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\n\\nFilters for tickets with any", + "title": "Transition (Beta) \u2014 DevRev | Docs" }, { - "id": "ART-1824_KNOWLEDGE_NODE-447", - "text": "the provided severities.\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\nFilters for records with any of the provided SLA stages.\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\nFilters for tickets with any of the provided source channels.\\nticket.subtype string Optional\\nFilters for tickets with any of the provided subtypes.\\ntype enum Optional\\nFilters for work of the provided types.\\nAllowed values: issue", - "title": "Delete \u2014 DevRev | Docs" + "id": "ART-1545_KNOWLEDGE_NODE-519", + "text": "response.\\n\\nticket.rev_org string Optional\\n\\nFilters for tickets that are associated with any of the provided Rev organizations.\\n\\nticket.severity enum Optional\\n\\nFilters for tickets with any of the provided severities.\\n\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\n\\nFilters for records with any of the provided SLA stages.\\n\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\n\\nFilters for tickets with any", + "title": "Create (Beta) \u2014 DevRev | Docs" }, { - "id": "ART-1829_KNOWLEDGE_NODE-463", - "text": "the provided severities.\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\nFilters for records with any of the provided SLA stages.\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\nFilters for tickets with any of the provided source channels.\\nticket.subtype string Optional\\nFilters for tickets with any of the provided subtypes.\\ntype enum Optional\\nFilters for work of the provided types.\\nAllowed values: issue", - "title": "Delete \u2014 DevRev | Docs" + "id": "ART-1560_KNOWLEDGE_NODE-521", + "text": "response.\\n\\nticket.rev_org string Optional\\n\\nFilters for tickets that are associated with any of the provided Rev organizations.\\n\\nticket.severity enum Optional\\n\\nFilters for tickets with any of the provided severities.\\n\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\n\\nFilters for records with any of the provided SLA stages.\\n\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\n\\nFilters for tickets with any", + "title": "Assign (Beta) \u2014 DevRev | Docs" }, { - "id": "ART-1837_KNOWLEDGE_NODE-447", - "text": "associated with any of the provided Rev organizations.\\nticket.severity enum Optional\\nFilters for tickets with any of the provided severities.\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\nFilters for records with any of the provided SLA stages.\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\nFilters for tickets with any of the provided source channels.\\nticket.subtype string Optional\\nFilters for tickets", - "title": "Update \u2014 DevRev | Docs" + "id": "ART-1027_KNOWLEDGE_NODE-6", + "text": "that intelligently assess ticket severity and streamline prioritization\\n* Specialized Computer CX Agents designed to handle both free and paid customer inquiries, optimizing deflection strategies for each segment\\n* In-app support experiences with real-time, contextual assistance\\n* Conversational AI layered on top of Computer\\xe2\\x80\\x99s Memory for unified knowledge\\n* Tight integration with Descope's internal dev workflows and APIs\\n\\nFor me, this is the number one priority for our service", + "title": "Descope streamlines support at scale with automation, AI, and unified collaboration" } ] }, @@ -1460,54 +1460,54 @@ "query": "support engineer typing indicator in ticket conversation", "retrievals": [ { - "id": "ART-6174_KNOWLEDGE_NODE-13", - "text": "creator](/docs/automations/smart-issue-creator)\\n - [Set user preference for group](/docs/automations/set-user-preference)\\n - [SLA status change Slack notifier](/docs/automations/sla-change-notifier)\\n - [Slash commands](/docs/automations/slash-commands)\\n - [Spam Shield](/docs/automations/spam-shield)\\n - [Subtype Migration](/docs/automations/subtype-migration)\\n - [Ticket age in engineering](/docs/automations/ticket-age-in-engineering)\\n - [Ticket issue field", - "title": "Conversation to ticket conversion | Conversations | Computer for Support Teams | DevRev" + "id": "ART-1969_KNOWLEDGE_NODE-28", + "text": "engineers. To get a list of the available commands, type / in a conversation response text box.\\n\\n\\xf0\\x9f\\x8e\\xab Tickets\\n---------\\n\\nThe benefit of Computer by DevRev is that conversations can be linked to support [tickets](../product/tickets), and tickets can be linked to build issues. This [linkage](../product/apps) means that all work can be traced back to customer concerns or requests.\\n\\nSlash commands are available in tickets to provide AI assistance to customer experience engineers.", + "title": "Computer for Support Teams | DevRev" }, { - "id": "ART-1960_KNOWLEDGE_NODE-41", - "text": "*[ticket](#ticket)*\\n: Read more about\\xc2\\xa0[*task*](https://docs.devrev.ai/product/core)\\n\\nticket\\n\\n: A record of a customer\\'s request for assistance or support.\\n: When a customer contacts a company with a problem or issue, the company creates a ticket to track the request and ensure that it is addressed in a timely and satisfactory manner. Also known as a \"customer ticket\" or \"support ticket\".\\n: Terms related to\\xc2\\xa0*ticket*:\\n\\n * *[conversation](#conversation)*\\n *", - "title": "Glossary | Computer by DevRev | DevRev" + "id": "ART-984_KNOWLEDGE_NODE-9", + "text": "support ticket to get an update on the status of this feature as well as asks their rep what is going on. In most cases the rep and support engineer don\\xe2\\x80\\x99t communicate or have the context of what the other is doing (let alone access to the other\\xe2\\x80\\x99s system). The support engineer may respond saying that feature is a long ways away, while the rep may say it\\xe2\\x80\\x99s \\xe2\\x80\\x9ccoming soon\\xe2\\x80\\x9d.\\n\\nThis lack of coordination leads to contradiction and a clear", + "title": "Why you Should be Looking at Support Differently" }, { - "id": "ART-1979_KNOWLEDGE_NODE-42", - "text": "it's automatically put into the *queued* stage, which indicates that it needs to be picked up by a customer experience engineer.\\n\\n**In-progress**\\n\\n* *Work in progress* (WIP)\\n\\n Work on the concern reported by the user has begun. When a customer experience engineer starts work on a ticket, the ticket's stage changes to *work in progress*. When they require more information, they may ask the customer for additional detail (such as logs or context), in which case the stage would change to", - "title": "Tickets | Computer for Support Teams | DevRev" + "id": "ART-1004_KNOWLEDGE_NODE-12", + "text": "The percentage of support tickets resolved by a support engineer during the first interaction with the customer, which can indicate the engineer\\xe2\\x80\\x99s efficiency and problem-solving abilities.\\n \\n \\n Calculation\\n \\n (Total number of tickets resolved on first contact by the engineer) / (Total number of tickets handled by the engineer) * 100\\n \\n \\n\\n\\nTraining Hours per Employee\\n\\n\\n Definition\\n \\n The average number of training hours completed by a", + "title": "Understanding a Support Engineer's Pain Points and KPIs" }, { - "id": "ART-1969_KNOWLEDGE_NODE-28", - "text": "engineers. To get a list of the available commands, type / in a conversation response text box.\\n\\n\\xf0\\x9f\\x8e\\xab Tickets\\n---------\\n\\nThe benefit of Computer by DevRev is that conversations can be linked to support [tickets](../product/tickets), and tickets can be linked to build issues. This [linkage](../product/apps) means that all work can be traced back to customer concerns or requests.\\n\\nSlash commands are available in tickets to provide AI assistance to customer experience engineers.", - "title": "Computer for Support Teams | DevRev" + "id": "ART-1981_KNOWLEDGE_NODE-26", + "text": "a small number of tags to help categorize tickets. For example, at DevRev we have the following: bug, feature-request, other-request, question, and incident.\\n* Designate one or more customer experience engineers to be on call. Add them to the **Support** group inside **Settings > Groups** and as default owner in the **Support Routing** snap-in. Default owners are notified through email and the DevRev app as soon as a new conversation is started.\\n\\nMonitor the inbox\\n-----------------\\n\\n*", + "title": "Support best practices | Computer for Support Teams | DevRev" }, { - "id": "ART-1979_KNOWLEDGE_NODE-38", - "text": "the top-right corner of your screen.\\n3. Add a title and description for your new ticket. You can also attach files related to the ticket in the description.\\n4. Select which part of the company/product this ticket is related to.\\n\\n ![]()\\n5. Enter other attributes for the ticket: change the assignee or accept the default; enter the severity; add any relevant tags to help employees identify any relevant traits of the ticket; select the workspace that the ticket pertains to.\\n6. If there are", - "title": "Tickets | Computer for Support Teams | DevRev" + "id": "ART-1003_KNOWLEDGE_NODE-18", + "text": "Response Time (FRT)\\n\\n\\n Definition\\n \\n The average time it takes for a support engineer to respond to a customer\\xe2\\x80\\x99s initial inquiry.\\n \\n \\n Calculation\\n \\n (Sum of response times for all first responses) / (Total number of first responses)\\n \\n \\n\\n\\nSELECT AVG(TIMESTAMPDIFF(MINUTE, t.created_at, r.created_at)) AS FirstResponseTime\\nFROM tickets t\\nJOIN responses r ON t.id = r.ticket_id\\nWHERE r.is_first_response = 1\\nAND EXTRACT(@period FROM", + "title": "Understanding a Support Lead's Pain Points and KPIs" }, { - "id": "ART-1977_KNOWLEDGE_NODE-13", - "text": "creator](/docs/automations/smart-issue-creator)\\n - [Set user preference for group](/docs/automations/set-user-preference)\\n - [SLA status change Slack notifier](/docs/automations/sla-change-notifier)\\n - [Slash commands](/docs/automations/slash-commands)\\n - [Spam Shield](/docs/automations/spam-shield)\\n - [Subtype Migration](/docs/automations/subtype-migration)\\n - [Ticket age in engineering](/docs/automations/ticket-age-in-engineering)\\n - [Ticket issue field", - "title": "Ticket-Team Performance | Support analytics | Computer for Support Teams | DevRev" + "id": "ART-6174_KNOWLEDGE_NODE-0", + "text": "b\"Conversation to ticket conversion | Conversations | Computer for Support Teams | DevRev\\n\\n* Computer\\n* Resources\\n* [Our Customers](/case-study)\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](/request-a-demo)\\n\\nComputer\\n\\nResources\\n\\n[Our Customers](/case-study)\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](/request-a-demo)\\n\\nSearch\\n\\n`CMD`\\xc2\\xa0+\\xc2\\xa0`K`\\n\\n* [Introduction](/docs)\\n* [Computer by DevRev](/docs/intro)\\n\\n + [Core concepts](/docs/product/core)\\n +", + "title": "Conversation to ticket conversion | Conversations | Computer for Support Teams | DevRev" }, { - "id": "ART-6174_KNOWLEDGE_NODE-36", - "text": "Status](/status)\\n\\n\\xc2\\xa9 2025 DevRev Inc.\\n\\n![]()\\n\\n![]()\"", - "title": "Conversation to ticket conversion | Conversations | Computer for Support Teams | DevRev" + "id": "ART-3880_KNOWLEDGE_NODE-8", + "text": "our users.\\n\\n![]()\\n\\nBrian MullinSr. Software Engineer, Orum\\n\\nOrum has especially benefited from the conversation feature, which connects to tickets but remains separate. Unlike their old system that locked agents into one-on-one support conversations, DevRev lets anyone handling a customer conversation tag teammates for help using internal comments. This creates a truly collaborative support environment.\\n\\nBy connecting teams and providing helpful context about each customer, DevRev has", + "title": "How Orum built a collaborative, AI-ready support engine" }, { - "id": "ART-2019_KNOWLEDGE_NODE-3", - "text": "reminder\\nCSAT on conversation\\nCSAT on ticket\\nDescope identity validation\\nFollow-up ticket\\nHTTP archive file upload & sanitization\\nLink preview\\nOrg tags sync\\nSentiment evaluator\\nStageFlow automator\\nSmart issue creator\\nSet user preference for group\\nSmart import KBs\\nSLA status change Slack notifier\\nSlash commands\\nSmart sprint\\nSpam Shield\\nTicket age in engineering\\nTicket issue field migrator\\nTicket email notifier\\nTask tracker\\nTicket Tagger\\nWork duration\\nOperational SLA", - "title": "Smart sprint | Automate | Snap-ins | DevRev" + "id": "ART-1870_KNOWLEDGE_NODE-5", + "text": "platform\\n----------------------------------------------------\\n\\nActionIQ selected DevRev to create a seamless connection between support and engineering operations. The implementation delivered:\\n\\n* **Unified ticket management:** A single environment for both customer support tickets and engineering incidents\\n* **Real-time visibility:** Clear insights into investigation status and engineering progress\\n* **Streamlined communication:** Integration with Slack channels synced into the DevRev", + "title": "Unifying teams: How ActionIQ transformed support with integration" }, { - "id": "ART-1979_KNOWLEDGE_NODE-41", - "text": "progress\\n\\n\\n\\nOpen\\n\\n\\n\\nEscalate\\n\\n\\n\\nValidate the fix\\n\\n\\n\\nAdditional detail needed\\n\\n\\n\\nCustomer responds\\n\\n\\n\\nStart\\n\\n\\n\\nFeature request accepted\\n\\n\\n\\nResolved\\n\\n\\n\\nNot valid\\n\\n\\n\\nQueued\\n\\n\\n\\nWork in progress\\n\\n\\n\\nAwaiting product assist\\n\\n\\n\\nAwaiting development\\n\\n\\n\\nAwating customer response\\n\\n\\n\\nIn development\\n\\n\\n\\nAccepted\\n\\n\\n\\nResolved\\n\\n\\n\\nCanceled\\n```\\n\\n**Open**\\n\\n* *Queued* (Q)\\n The initial stage for all tickets. When a new ticket is created,", - "title": "Tickets | Computer for Support Teams | DevRev" + "id": "ART-1004_KNOWLEDGE_NODE-9", + "text": "tickets\\nWHERE EXTRACT(@period FROM created_at) = EXTRACT(@period FROM CURRENT_DATE)\\nGROUP BY engineer_id;\\n-- NOTE: Replace @period with 'DAY', 'WEEK', 'MONTH', or 'QUARTER'.\\n\\n\\nIndividual Customer Satisfaction (CSAT) Score\\n\\n\\n Definition\\n \\n A metric that gauges customer satisfaction with the support provided by a specific engineer, typically collected through surveys.\\n \\n \\n Calculation\\n \\n (Number of satisfied responses for the engineer) / (Total number of", + "title": "Understanding a Support Engineer's Pain Points and KPIs" }, { - "id": "ART-1979_KNOWLEDGE_NODE-45", - "text": "a user. In certain cases where the ticket depends on some fix (issues) the stage may go from *in development* to *awaiting customer response* when the corresponding issues have been resolved and the fix needs to be validated with the user.\\n\\n In certain cases, the customer experience engineer may be able to solve directly (without any required issues) which may change the stage from *work in progress* to *awaiting customer response* to validate they have solved the problem. If either has", - "title": "Tickets | Computer for Support Teams | DevRev" + "id": "ART-4271_KNOWLEDGE_NODE-29", + "text": "end user.\\n\\n## Why you should convert a Conversation to a Ticket\\n\\nConsider converting a conversation to a ticket in these scenarios:\\n\\n * **Complex issues** : When a customer inquiry requires in-depth investigation that can't be resolved in a quick conversation.\\n * **Cross-team collaboration** : Issues requiring input from multiple departments or specialists.\\n * **Escalation needs** : When a conversation needs to be escalated to a higher support tier.\\n * **Feature requests** :", + "title": "Convert Conversations to Tickets | Conversations | Support | DevRev" } ] }, @@ -1516,54 +1516,54 @@ "query": "update the name that a broadcast on an incident comes from when pushed to a ticket", "retrievals": [ { - "id": "ART-4133_KNOWLEDGE_NODE-18", - "text": "incident was mitigated.\\n\\nowned\\\\_byobjectOptional\\n\\nShow 1 properties\\n\\npiaobjectOptional\\n\\nShow 1 properties\\n\\nplaybooksobjectOptional\\n\\nShow 1 properties\\n\\nrelated\\\\_docsobjectOptional\\n\\nShow 1 properties\\n\\nreported\\\\_bylongOptional\\n\\nThe entity that first reported the incident.\\n\\nseveritylongOptional\\n\\nSeverity of the incident.\\n\\nstageobjectOptional\\n\\nUpdate object for Stage.\\n\\nShow 2 properties\\n\\nstage\\\\_validation\\\\_optionslist of enumsOptional\\n\\nThe type of stage", - "title": "Update Incident | DevRev | Docs" + "id": "ART-1979_KNOWLEDGE_NODE-26", + "text": "associated with a part (product or service) and can come from both internal and external users. Tickets are also used to communicate progress to the user or other impacted party.\\n\\nThere may be cases where mass communications (broadcast) are necessary in the event of lots of impacted or related parties (such as service status updates). In this scenario, the ticket would be used to broadcast and handle communications among multiple parties, including across multiple workspaces. Broadcast can", + "title": "Tickets | Computer for Support Teams | DevRev" }, { - "id": "ART-4133_KNOWLEDGE_NODE-1", - "text": "\" \\\\ |\\n| > | -H \"Content-Type: application/json\" \\\\ |\\n| > | -d \\'{ |\\n| > | \"id\": \"string\" |\\n| > | }\\' |\\n```\\n\\n[Try it](/beta/api-reference/incidents/update?explorer=true)\\n\\n200Successful\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | { |\\n| 2 | \"incident\": { |\\n| 3 | \"id\": \"string\", |\\n| 4 | \"title\": \"string\", |\\n| 5 | \"acknowledged_date\": \"2023-01-01T12:00:00.000Z\", |\\n| 6 | \"actual_close_date\": \"2023-01-01T12:00:00.000Z\", |\\n| 7 | \"applies_to_parts\": [ |\\n| 8 | { |\\n| 9 | \"display_id\":", - "title": "Update Incident | DevRev | Docs" + "id": "ART-17231_KNOWLEDGE_NODE-69", + "text": "#record:incident #record:issue #record:opportunity #record:product #record:project #record:revu #record:task #record:ticket] | \\xe2\\x9c\\x94\\xef\\xb8\\x8e | Target object ID |\\n\\n#### Enum values\\n\\n**link\\\\_type\\\\_id**\\n\\n| Value | Name | Description |\\n| --- | --- | --- |\\n| `is_dependent_on` | Is Dependent On | - |\\n| `is_duplicate_of` | Is Duplicate Of | - |\\n| `is_parent_of` | Is Parent Of | - |\\n| `is_related_to` | Is Related To | - |\\n\\n[\\xe2\\x96\\xb2", + "title": "Supported DevRev object types | DevRev | Docs" }, { - "id": "ART-4133_KNOWLEDGE_NODE-5", - "text": "|\\n| 67 | \"display_id\": \"string\", |\\n| 68 | \"identified_date\": \"2023-01-01T12:00:00.000Z\", |\\n| 69 | \"impact\": { |\\n| 70 | \"count\": { |\\n| 71 | \"id\": 1, |\\n| 72 | \"label\": \"string\", |\\n| 73 | \"ordinal\": 1, |\\n| 74 | \"value\": null |\\n| 75 | }, |\\n| 76 | \"customer_ids\": [ |\\n| 77 | { |\\n| 78 | \"id\": \"string\", |\\n| 79 | \"display_id\": \"string\", |\\n| 80 | \"display_name\": \"string\" |\\n| 81 | } |\\n| 82 | ] |\\n| 83 | }, |\\n| 84 | \"mitigated_date\": \"2023-01-01T12:00:00.000Z\", |\\n| 85 | \"modified_by\": {", - "title": "Update Incident | DevRev | Docs" + "id": "ART-1483_KNOWLEDGE_NODE-18", + "text": "the code\\n\\nUpdate the code in `src/functions/ticket_creator/index.ts` to reflect the behavior.\\n\\nFirstly, import the DevRev TypeScript SDK in the `index.ts` file\\n\\nindex.ts\\n\\n[code]\\n\\n 1| import {client, publicSDK} from \"@devrev/typescript-sdk\"; \\n ---|---\\n[/code] \\n \\nNext, update the `run` function in the hello-world example. Since the ticket gets created frequently, set some creation time in the title and the body. The example uses the part as `PROD-1` and keeps the owner as", + "title": "Using a snap-in to perform a DevRev action \u2014 DevRev | Docs" }, { - "id": "ART-4133_KNOWLEDGE_NODE-15", - "text": "\"string\" |\\n| 258 | } |\\n| 259 | ], |\\n| 260 | \"target_close_date\": \"2023-01-01T12:00:00.000Z\" |\\n| 261 | } |\\n| 262 | } |\\n```\\n\\nUpdates an incident.\\n\\n### Headers\\n\\nAuthorizationstringRequired\\n\\nBearer authentication of the form `Bearer `, where token is your auth token.\\n\\n### Request\\n\\nThis endpoint expects an object.\\n\\nidstringRequired`format: \"id\"`\\n\\nThe ID of the incident to be updated.\\n\\nacknowledged\\\\_datestringOptional`format: \"date-time\"`\\n\\nTimestamp when the incident", - "title": "Update Incident | DevRev | Docs" + "id": "ART-1805_KNOWLEDGE_NODE-194", + "text": "Update.\\n\\nPOST https:// api.devrev.ai / incidents.update\\nUpdates an incident.\\nRequest.\\n\\nThis endpoint expects an object.\\nid string Required\\nThe ID of the incident to be updated.\\nacknowledged_date datetime Optional\\nTimestamp when the incident was acknowledged.\\napplies_to_parts object Optional\\nShow property\\nartifacts object Optional\\nShow property\\nbody string Optional\\nBody of the incident.\\ncustom_fields map from strings to any Optional\\nApplication-defined custom", + "title": "List Post \u2014 DevRev | Docs" }, { - "id": "ART-4127_KNOWLEDGE_NODE-5", - "text": "|\\n| 67 | \"display_id\": \"string\", |\\n| 68 | \"identified_date\": \"2023-01-01T12:00:00.000Z\", |\\n| 69 | \"impact\": { |\\n| 70 | \"count\": { |\\n| 71 | \"id\": 1, |\\n| 72 | \"label\": \"string\", |\\n| 73 | \"ordinal\": 1, |\\n| 74 | \"value\": null |\\n| 75 | }, |\\n| 76 | \"customer_ids\": [ |\\n| 77 | { |\\n| 78 | \"id\": \"string\", |\\n| 79 | \"display_id\": \"string\", |\\n| 80 | \"display_name\": \"string\" |\\n| 81 | } |\\n| 82 | ] |\\n| 83 | }, |\\n| 84 | \"mitigated_date\": \"2023-01-01T12:00:00.000Z\", |\\n| 85 | \"modified_by\": {", - "title": "Create Incident | DevRev | Docs" + "id": "ART-1789_KNOWLEDGE_NODE-193", + "text": "Update.\\n\\nPOST https:// api.devrev.ai / incidents.update\\nUpdates an incident.\\nRequest.\\n\\nThis endpoint expects an object.\\nid string Required\\nThe ID of the incident to be updated.\\nacknowledged_date datetime Optional\\nTimestamp when the incident was acknowledged.\\napplies_to_parts object Optional\\nShow property\\nartifacts object Optional\\nShow property\\nbody string Optional\\nBody of the incident.\\ncustom_fields map from strings to any Optional\\nApplication-defined custom", + "title": "List \u2014 DevRev | Docs" }, { - "id": "ART-1551_KNOWLEDGE_NODE-275", - "text": "Optional\\n\\nTimestamp when the incident was mitigated.\\n\\nowned_by object Optional\\nShow property\\npia object Optional\\nShow property\\nplaybooks object Optional\\nShow property\\nrelated_docs object Optional\\nShow property\\nreported_by long Optional\\n\\nThe entity that first reported the incident.\\n\\nseverity long Optional\\n\\nSeverity of the incident.\\n\\nsource long Optional\\n\\nSource of where the incident was created. Only sys users and service accounts are supposed to set this field.\\n\\nstage", - "title": "Update (Beta) \u2014 DevRev | Docs" + "id": "ART-1307_KNOWLEDGE_NODE-194", + "text": "Update.\\n\\nPOST https:// api.devrev.ai / incidents.update\\nUpdates an incident.\\nRequest.\\n\\nThis endpoint expects an object.\\nid string Required\\nThe ID of the incident to be updated.\\nacknowledged_date datetime Optional\\nTimestamp when the incident was acknowledged.\\napplies_to_parts object Optional\\nShow property\\nartifacts object Optional\\nShow property\\nbody string Optional\\nBody of the incident.\\ncustom_fields map from strings to any Optional\\nApplication-defined custom", + "title": "List Post \u2014 DevRev | Docs" }, { - "id": "ART-4127_KNOWLEDGE_NODE-10", - "text": "\"string\" |\\n| 166 | }, |\\n| 167 | \"sync_metadata\": { |\\n| 168 | \"external_reference\": \"string\", |\\n| 169 | \"origin_system\": \"string\" |\\n| 170 | }, |\\n| 171 | \"title\": \"string\" |\\n| 172 | } |\\n| 173 | ], |\\n| 174 | \"reported_by\": { |\\n| 175 | \"id\": 1, |\\n| 176 | \"label\": \"string\", |\\n| 177 | \"ordinal\": 1, |\\n| 178 | \"value\": null |\\n| 179 | }, |\\n| 180 | \"severity\": { |\\n| 181 | \"id\": 1, |\\n| 182 | \"label\": \"string\", |\\n| 183 | \"ordinal\": 1, |\\n| 184 | \"value\": null |\\n| 185 | }, |\\n| 186 |", - "title": "Create Incident | DevRev | Docs" + "id": "ART-1788_KNOWLEDGE_NODE-193", + "text": "Update.\\n\\nPOST https:// api.devrev.ai / incidents.update\\nUpdates an incident.\\nRequest.\\n\\nThis endpoint expects an object.\\nid string Required\\nThe ID of the incident to be updated.\\nacknowledged_date datetime Optional\\nTimestamp when the incident was acknowledged.\\napplies_to_parts object Optional\\nShow property\\nartifacts object Optional\\nShow property\\nbody string Optional\\nBody of the incident.\\ncustom_fields map from strings to any Optional\\nApplication-defined custom", + "title": "Get Post \u2014 DevRev | Docs" }, { - "id": "ART-4133_KNOWLEDGE_NODE-10", - "text": "\"string\" |\\n| 166 | }, |\\n| 167 | \"sync_metadata\": { |\\n| 168 | \"external_reference\": \"string\", |\\n| 169 | \"origin_system\": \"string\" |\\n| 170 | }, |\\n| 171 | \"title\": \"string\" |\\n| 172 | } |\\n| 173 | ], |\\n| 174 | \"reported_by\": { |\\n| 175 | \"id\": 1, |\\n| 176 | \"label\": \"string\", |\\n| 177 | \"ordinal\": 1, |\\n| 178 | \"value\": null |\\n| 179 | }, |\\n| 180 | \"severity\": { |\\n| 181 | \"id\": 1, |\\n| 182 | \"label\": \"string\", |\\n| 183 | \"ordinal\": 1, |\\n| 184 | \"value\": null |\\n| 185 | }, |\\n| 186 |", - "title": "Update Incident | DevRev | Docs" + "id": "ART-1300_KNOWLEDGE_NODE-193", + "text": "Update.\\n\\nPOST https:// api.devrev.ai / incidents.update\\nUpdates an incident.\\nRequest.\\n\\nThis endpoint expects an object.\\nid string Required\\nThe ID of the incident to be updated.\\nacknowledged_date datetime Optional\\nTimestamp when the incident was acknowledged.\\napplies_to_parts object Optional\\nShow property\\nartifacts object Optional\\nShow property\\nbody string Optional\\nBody of the incident.\\ncustom_fields map from strings to any Optional\\nApplication-defined custom", + "title": "Create \u2014 DevRev | Docs" }, { - "id": "ART-4133_KNOWLEDGE_NODE-17", - "text": "included in the\\nspecifier, it remains unchanged. For surfaces with human interactors,\\nit is recommended to provide tenant\\\\_fragment: true and\\nvalidate\\\\_required\\\\_fields: true.\\n\\nShow 5 properties\\n\\nexternal\\\\_source\\\\_dataobjectOptional\\n\\nShow 3 properties\\n\\nidentified\\\\_datestringOptional`format: \"date-time\"`\\n\\nTime when the incident was identified/reported.\\n\\nimpactobjectOptional\\n\\nShow 2 properties\\n\\nmitigated\\\\_datestringOptional`format: \"date-time\"`\\n\\nTimestamp when the", - "title": "Update Incident | DevRev | Docs" + "id": "ART-1979_KNOWLEDGE_NODE-27", + "text": "also be used to engage customers for feedback/ideas (such as new feature ideas). Scoping is important for broadcast tickets as there needs to be a differentiation between broadcast (all revs) vs. multicast (particular revs).\\n\\nViews of tickets can be found under **Support** in the DevRev app.\\n\\n![]()\\n\\nYou can export views to CSV or JSON by selecting **Actions** in the upper-right corner and choosing the format.\\n\\nAttributes\\n----------\\n\\nTickets have attributes that can be used to filter", + "title": "Tickets | Computer for Support Teams | DevRev" }, { - "id": "ART-4133_KNOWLEDGE_NODE-19", - "text": "validations options when updating the stage or\\nthe stage diagram of an incident.\\n\\nAllowed values:allow\\\\_invalid\\\\_transition\\n\\nstaged\\\\_infoobjectOptional\\n\\nUpdate object for StagedInfo.\\n\\nShow 4 properties\\n\\nsync\\\\_metadataobjectOptional\\n\\nShow 4 properties\\n\\ntagsobjectOptional\\n\\nShow 1 properties\\n\\ntarget\\\\_close\\\\_datestringOptional`format: \"date-time\"`\\n\\nTimestamp when the incident is expected to be resolved.\\n\\ntitlestringOptional`format: \"text\"`\\n\\nTitle of the", - "title": "Update Incident | DevRev | Docs" + "id": "ART-1981_KNOWLEDGE_NODE-26", + "text": "a small number of tags to help categorize tickets. For example, at DevRev we have the following: bug, feature-request, other-request, question, and incident.\\n* Designate one or more customer experience engineers to be on call. Add them to the **Support** group inside **Settings > Groups** and as default owner in the **Support Routing** snap-in. Default owners are notified through email and the DevRev app as soon as a new conversation is started.\\n\\nMonitor the inbox\\n-----------------\\n\\n*", + "title": "Support best practices | Computer for Support Teams | DevRev" } ] }, @@ -1572,14 +1572,14 @@ "query": "search functionality on tickets and issues deprecated", "retrievals": [ { - "id": "ART-1959_KNOWLEDGE_NODE-29", - "text": "in:title crm |\\n| - | Acts as an exclusion in search results. \"-\" can be used for the same purpose. | type:issue -crm type:issue in:title -crm |\\n| state | Filters results based on the stage: open, closed, or in\\\\_progress. | state:open state:closed state:in\\\\_progress |\\n| severity | Filters out tickets with the desired severity level. Supports: blocker, high, medium, low. | severity:high type:ticket -severity:low (filters all tickets excluding the ones with low severity)", - "title": "Search | Computer by DevRev | DevRev" + "id": "ART-1949_KNOWLEDGE_NODE-28", + "text": "Click **Delete** to confirm.\\n\\nSearch\\n------\\n\\nYou can search an object (issue, ticket, conversation) in a vista by clicking the search icon which is to the left of the **@** button in the vista toolbar.\\nYou can enter the description or name of the object which brings it up directly without issue or ticket number.\\n\\n![]()\\n\\nVista sharing\\n-------------\\n\\nVistas are private by default, ensuring they are accessible only to you unless explicitly shared. You can now share your vistas with", + "title": "Vistas | Computer by DevRev | DevRev" }, { - "id": "ART-1959_KNOWLEDGE_NODE-28", - "text": "of the ticket/issue/enhancement or title. | in:title crm in:title \"crm exp\" in:title crm exp in:body \"bot issues\" |\\n| type: | Enables users to filter by object type. Supported object types include: issue, enhancement, ticket, revu (for searching contacts), question\\\\_answer, conversation, article, devu (for searching internal contacts), account, feature, runnable. | type:issue type:enhancement in:title CRM type:revu type:enhancement, opportunity type:issue, enhancement", - "title": "Search | Computer by DevRev | DevRev" + "id": "ART-17515_KNOWLEDGE_NODE-26", + "text": "and feature requests on tickets.\\n* Computer on Plug: Enhances the following functionalities:\\n\\n + Conversation: It deflects customer queries using your knowledge base, providing accurate and relevant responses.\\n + Search: It summarizes your search results, making information retrieval more efficient and user-friendly.\\n* Computer assist: Recommends relevant articles and similar work items.\\n* Slack tickets: Automatically generates titles and descriptions for tickets created from Slack", + "title": "AI use cases in DevRev | Computer by DevRev | DevRev" }, { "id": "ART-1242_KNOWLEDGE_NODE-0", @@ -1587,39 +1587,39 @@ "title": "Tickets and issues | DevRev | Docs" }, { - "id": "ART-1959_KNOWLEDGE_NODE-34", - "text": "subtype: :\\n```\\n```\\n\\n**Examples**\\n\\nSearch for tickets related to access issues with tenant field escalated:\\n\\n```\\n```\\n1 tnt__escalated:true access issues\\n```\\n```\\n\\nSearch for bugs related to access issues with subtype field customer\\\\_impact:\\n\\n```\\n```\\n1 subtype:Bug ctype__customer_impact:true access issues\\n```\\n```\\n\\nSearch across multiple subtypes for tickets related to access issues:\\n\\n```\\n```\\n1 subtype:Bug,Events access", - "title": "Search | Computer by DevRev | DevRev" + "id": "ART-15716_KNOWLEDGE_NODE-8", + "text": "for TicketsWe have a summarize option (it would resemble sparkle symbol) in the top right corner of the ticket view, which uses the ticket content to summarize the ticket\\n\\n7. Difference between Issues and Tickets\\n\\nTickets\\xc2\\xa0are for customer support\\xe2\\x80\\x94tracking requests, problems, or questions from customers or prospects.\\n\\nIssues\\xc2\\xa0are internal work items for developers\\xe2\\x80\\x94used to improve the product, fix bugs, or implement features. Issues can be linked to", + "title": "Support queries related playbook" }, { - "id": "ART-1784_KNOWLEDGE_NODE-445", - "text": "issues synced from this specific origin system.\\ntags string Optional\\nFilters for work with any of the provided tags.\\nticket.channels enum Optional\\nFilters for tickets with any of the provided channels.\\nAllowed values: email plug slack twilio twilio_sms\\nticket.group string Optional\\nFilters for tickets belonging to specific groups.\\nticket.is_spam boolean Optional\\nFilters for tickets that are spam.\\nticket.needs_response boolean Optional\\nFilters for tickets that need", - "title": "Locate Post \u2014 DevRev | Docs" + "id": "ART-1241_KNOWLEDGE_NODE-7", + "text": "helpful?\\n\\nYesNo\\n\\n[Previous](/api-reference/webhooks/list-post)[#### Tickets and issues\\n\\nNext](/api-reference/works/tickets-and-issues)[Built with](https://buildwithfern.com/?utm_campaign=buildWith&utm_medium=docs&utm_source=developer.devrev.ai)'", + "title": "Update Webhook | DevRev | Docs" }, { - "id": "ART-1783_KNOWLEDGE_NODE-445", - "text": "issues synced from this specific origin system.\\ntags string Optional\\nFilters for work with any of the provided tags.\\nticket.channels enum Optional\\nFilters for tickets with any of the provided channels.\\nAllowed values: email plug slack twilio twilio_sms\\nticket.group string Optional\\nFilters for tickets belonging to specific groups.\\nticket.is_spam boolean Optional\\nFilters for tickets that are spam.\\nticket.needs_response boolean Optional\\nFilters for tickets that need", - "title": "Locate \u2014 DevRev | Docs" + "id": "ART-1949_KNOWLEDGE_NODE-26", + "text": "upper-right corner after you make a change.\\n You can toggle on **Show groups** in **Group by** dropdown to open up a side panel showing the groups.\\n\\n![]()\\n\\n![]()\\n\\nYou can also apply **Actions** > **Smart Clustering** if the number of tickets or issues is under 10,000. Clustering isn't available for conversations.\\n\\n1. Click **Save as**. You can give the list a name, and description and save it which causes it to show up in the **My list** section at the bottom of the left-side nav", + "title": "Vistas | Computer by DevRev | DevRev" }, { - "id": "ART-1447_KNOWLEDGE_NODE-1", - "text": "[Tickets](https://docs.devrev.ai/product/tickets) and [Issues](https://docs.devrev.ai/product/issues).\\n\\nWas this page helpful?YesNo\\n\\n[Create WorkUp Next](/public/api-reference/works/create)\\n\\n[Built with](https://buildwithfern.com/?utm_campaign=buildWith&utm_medium=docs&utm_source=developer.devrev.ai)\\n\\n[Enterprise grade security to protect customer dataLearn more about it.](https://devrev.ai/blog/soc-compliance)\\n\\nProduct\\n\\n * [Build](https://devrev.ai/build)\\n *", - "title": "Tickets and issues \u2014 DevRev | Docs" + "id": "ART-15687_KNOWLEDGE_NODE-14", + "text": "engineering](/docs/automations/ticket-age-in-engineering)\\n - [Ticket issue field migrator](/docs/automations/ticket-issue-field-migrator)\\n - [Ticket Immutability](/docs/automations/ticket-immutability)\\n - [Ticket email notifier](/docs/automations/ticket-email-notifier)\\n - [Task tracker](/docs/automations/task-tracker)\\n - [Ticket Tagger](/docs/automations/ticket-tagger)\\n - [Tracxn sync](/docs/automations/tracxn-sync)\\n - [User group", + "title": "Dashboards | Computer by DevRev | DevRev" }, { - "id": "ART-1447_KNOWLEDGE_NODE-0", - "text": "b'[](/public/api-reference/works/tickets-and-issues)\\n\\nPublic\\n\\n[API Reference](/public/api-reference/getting-started)[Works](/public/api-reference/works/tickets-and-issues)\\n\\n#\\n\\nTickets and issues\\n\\n`works` endpoint\\n\\n\\xe2\\x84\\xb9\\xef\\xb8\\x8f A work item is a record of some work that has to be done for a customer (ticket) or for another builder or maintainer of a part (issue).\\n\\n\\xf0\\x9f\\x93\\x8c For more information about work items, refer to", - "title": "Tickets and issues \u2014 DevRev | Docs" + "id": "ART-15664_KNOWLEDGE_NODE-13", + "text": "\\n\\nYou may want to restrict links to specific subtypes of objects. For example, only allowing issues\\nof a particular subtype to be linked to tickets.\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl --location \\'https://api.devrev.ai/link-types.custom.create\\' \\\\ |\\n| > | --header \\'Content-Type: application/json\\' \\\\ |\\n| > | --header \\'Authorization: Bearer \\' \\\\ |\\n| > | --data \\'{ |\\n| > | \"name\": \"Link between social media issues and tickets\", |\\n| > | \"source_types\": [ |\\n| > | { |\\n|", + "title": "Links | DevRev | Docs" }, { - "id": "ART-2874_KNOWLEDGE_NODE-27", - "text": "updated, and not updated. If the fields specified in the configuration are not found, a notification will be provided in the **Discussion** tab.\\n\\n[PreviousTicket age in engineering](/docs/automations/ticket-age-in-engineering)[NextTicket Immutability](/docs/automations/ticket-immutability)\\n\\n#### On this page\\n\\n* [Ticket issue field migrator](#ticket-issue-field-migrator)\\n* [Installation](#installation)\\n* [Configuration](#configuration)\\n\\n[Enterprise grade security to protect customer", - "title": "Ticket issue field migrator | Automate | Snap-ins | DevRev" + "id": "ART-10697_KNOWLEDGE_NODE-30", + "text": "New filtering options let agents view tickets tied to specific articles, while updated analytics reveal the most and least linked articles, improving knowledge sharing and support strategy.\\n* Plug is our live chat widget designed for real-time conversations in your customer portal. It reduces ticket volume by resolving common queries instantly, enhancing self-service and speeding up issue resolution. Use spotlight cards or banners to notify customers about incidents, updates, or promotions,", + "title": "February 2025 | Changelog | DevRev" }, { - "id": "ART-1959_KNOWLEDGE_NODE-5", - "text": "ticket conversion](/docs/product/conversation-ticket)\\n + [Tickets](/docs/product/tickets)\\n + [Routing](/docs/product/routing)\\n + [Support best practices](/docs/product/support-bp)\\n + [Customer portal](/docs/product/support-portal)\\n + [Questions & answers](/docs/product/qa)\\n + [Knowledge Base](/docs/product/knowledge-base)\\n\\n - [Articles](/docs/product/articles)\\n - [Collections](/docs/product/collection)\\n + [Turing AI agent](/docs/product/conversational-bot)\\n\\n - [Best", - "title": "Search | Computer by DevRev | DevRev" + "id": "ART-2024_KNOWLEDGE_NODE-27", + "text": "help now... ask again in 5d\\n\\nSample response:\\n\\n> I am unable to assist you at the moment, however please reach out to me again in five days and I will be happy to help you.\\n\\n### Summarize\\n\\nUsing the summarize command, you can sum up the entire conversation. It applies to the following:\\n\\n* Conversation\\n* Tickets\\n* Issues\\n* Part\\n* Workspace\\n* Customer\\n* Account\\n\\nSample response:\\n\\n> **Summary:**\\n>\\n> * Rahul from DummyOrg is having difficulty installing the Plug Widget.\\n> *", + "title": "Slash commands | Automate | Snap-ins | DevRev" } ] }, @@ -1627,55 +1627,55 @@ "query_id": "3c9dd52b-a637-4fa2-8bd7-a42ec07c7655", "query": "how to use snap-ins in DevRev", "retrievals": [ + { + "id": "ART-2913_KNOWLEDGE_NODE-25", + "text": "DevRev support.\\n\\nInstallation\\n------------\\n\\n1. In DevRev, go to **Settings** > **Snap-ins** and click **Explore\\n Marketplace** in the top-right corner.\\n2. In the DevRev marketplace, find **PagerDuty** and click **Install**.\\n3. Set-up the snap-in's configurations.\\n4. Click **Save** > **Install snap-in**.\\n5. Execute the /pagerduty register-webhook command in the snap-in\\n **Discussions** tab. Upon successful start, you will see the message\\n **Successfully registered DevRev", + "title": "PagerDuty | Integrate | Snap-ins | DevRev" + }, { "id": "ART-1274_KNOWLEDGE_NODE-1", "text": "snap-in.\\n\\nSnap-ins are collections of objects that extend DevRev\\xe2\\x80\\x99s core platform value. These objects include automation, event sources, keyrings, custom types, and vistas. Snap-ins are packaged and installed separately from the DevRev core platform. To create your own snap-in, create a [dev org](https://app.devrev.ai/) where you will be installing your snap-in.\\n\\n[1](/snapin-development/tutorials/getting-started#before-you-begin)\\n\\n### Before you begin\\n\\n* Install [DevRev", "title": "Getting started | DevRev | Docs" }, { - "id": "ART-1275_KNOWLEDGE_NODE-0", - "text": "b'Using a snap-in to perform a DevRev action | DevRev | Docs\\n\\n[![]()![]()](https://developer.devrev.ai/)\\n\\nPublic\\n\\nPublic\\n\\nSearch\\n\\n`/`\\n\\nOn this page\\n\\n* [Introduction](/snapin-development/tutorials/timer-ticket-creator#introduction)\\n* [Background context](/snapin-development/tutorials/timer-ticket-creator#background-context)\\n* [Resources](/snapin-development/tutorials/timer-ticket-creator#resources)\\n\\n[Snap-in", - "title": "Using a snap-in to perform a DevRev action | DevRev | Docs" - }, - { - "id": "ART-1483_KNOWLEDGE_NODE-31", - "text": "__\\n\\n[Pricing](https://devrev.ai/pricing)\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](https://devrev.ai/request-a-demo)\\n\\n'", - "title": "Using a snap-in to perform a DevRev action \u2014 DevRev | Docs" + "id": "ART-1470_KNOWLEDGE_NODE-5", + "text": "keyrings, custom types, and vistas. Snap-ins are packaged and installed separately from the DevRev core platform. To create your own snap-in, create a [dev org](https://app.devrev.ai/) where you will be installing your snap-in.\\n\\n[1](/public/snapin-development/tutorials/getting-started#before-you-begin)\\n\\n### Before you begin\\n\\n * Install [DevRev CLI](/public/snapin-development/references/cli-install)\\n * Install", + "title": "Getting started \u2014 DevRev | Docs" }, { - "id": "ART-1485_KNOWLEDGE_NODE-5", - "text": "[Resources](/public/snapin-development/tutorials/triggered-event#resources)\\n\\n[Snap-in development](/public/snapin-development/concepts)[Tutorials](/public/snapin-development/tutorials/overview)\\n\\n#\\n\\nSnap-in triggered by a DevRev event\\n\\n## Introduction\\n\\nIn this tutorial, you\\xe2\\x80\\x99ll learn to create a dynamic snap-in that responds to both DevRev Webhook events triggered by the creation of a [work](https://docs.devrev.ai/product/core) and specialized", - "title": "Snap-in triggered by a DevRev event \u2014 DevRev | Docs" + "id": "ART-1280_KNOWLEDGE_NODE-13", + "text": "| --- |\\n| $ | devrev snap_in_version list | jq . |\\n```\\n\\n**Additional flags**:\\n\\n* `--package `: Optional. If not provided, it uses the id from the [snap-in context](/snapin-development/references/cli#snap-in-context).\\n\\nSnap-in\\n-------\\n\\n###### Create a snap-in draft\\n\\nTo create a snap-in draft instance, run the following command:\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | devrev snap_in draft --snap_in_version [id] |\\n```\\n\\nFor example:\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | devrev", + "title": "DevRev CLI reference | DevRev | Docs" }, { - "id": "ART-1483_KNOWLEDGE_NODE-27", - "text": "Program](https://devrev.ai/startups)\\n\\nCompany\\n\\n * [About](https://devrev.ai/about)\\n * [People](https://devrev.ai/people)\\n * [Careers](https://devrev.ai/careers)\\n * [Places](https://devrev.ai/places)\\n * [Invest](https://revd.devrev.ai/)\\n * [What Why How](https://devrev.ai/what-why-how)\\n\\nConnect\\n\\n * [Contact ](mailto:humansofdevrev@devrev.ai)\\n * [Instagram ](https://www.instagram.com/devrev)\\n * [Medium ](https://medium.com/devrev)\\n * [Linkedin", - "title": "Using a snap-in to perform a DevRev action \u2014 DevRev | Docs" + "id": "ART-1280_KNOWLEDGE_NODE-21", + "text": "devrev snap_in_context show |\\n| > | snap_in_context: |\\n| > | snap_in: don:integration::devo/:snap_in/ |\\n| > | snap_in_package: don:integration::devo/:snap_in_package/ |\\n| > | snap_in_version: don:integration::devo/:snap_in_package/:snap_in_version/ |\\n```\\n\\n###### List the snap-in context\\n\\nTo list the snap-in context, run the following", + "title": "DevRev CLI reference | DevRev | Docs" }, { - "id": "ART-2004_KNOWLEDGE_NODE-24", - "text": "the [Marketplace](/marketplace).\\n\\nSnap-ins are of the following types:\\n\\n* **Integrations** let you connect DevRev with existing systems such as Slack and Jira.\\n* **Automations** perform tasks within DevRev based on events, like responding to customer conversations and linking tickets and issues.\\n* **AirSync** helps you bring data from external sources to DevRev and keep them in sync.\\n\\nWhile numerous snap-ins are available and more are in development, you can create your own using", - "title": "Snap-ins | DevRev" + "id": "ART-17214_KNOWLEDGE_NODE-1", + "text": "developing your snap-in with a `manifest.yaml` file. The manifest defines the snap-in\\xe2\\x80\\x99s configuration, including its name, description, version, connection details, and functionality.\\n\\nBegin by setting the values for `name` and `description` in the template.\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | name: Template Connector |\\n| 2 | description: Template Connector for importing dummy data into DevRev |\\n```\\n\\n### Set snap-in functionalities\\n\\nDevRev supports creating snap-ins for", + "title": "Manifest | DevRev | Docs" }, { - "id": "ART-1277_KNOWLEDGE_NODE-1", - "text": "development](/snapin-development/concepts)[Tutorials](/snapin-development/tutorials/overview)\\n\\nSnap-in triggered by a DevRev event\\n===================================\\n\\nCopy page\\n\\nIntroduction\\n------------\\n\\nIn this tutorial, you\\xe2\\x80\\x99ll learn to create a dynamic snap-in that responds to both DevRev Webhook events triggered by the creation of a [work](https://docs.devrev.ai/product/core) and specialized [command](/snapin-development/references/commands) within DevRev.\\n\\nThe focus", - "title": "Snap-in triggered by a DevRev event | DevRev | Docs" + "id": "ART-1468_KNOWLEDGE_NODE-5", + "text": "\\xe2\\x80\\x9carms-length\\xe2\\x80\\x9d and without making any changes to DevRev\\xe2\\x80\\x99s core platform.\\n\\nSnap-in developers interact with DevRev objects through APIs, get updates on DevRev objects through webhooks, and register an event source to subscribe to GitHub/Slack/any external events.\\n\\n## Snap-in package\\n\\nA snap-in package is a collection of DevRev objects and their relationships that describe the functionality of the developed snap-in. It doesn\\xe2\\x80\\x99t reference an object", + "title": "Concepts \u2014 DevRev | Docs" }, { - "id": "ART-1277_KNOWLEDGE_NODE-4", - "text": "[Using a snap-in to perform a DevRev action](/snapin-development/tutorials/timer-ticket-creator) tutorial.\\n\\n[1](/snapin-development/tutorials/triggered-event#installation-guide)\\n\\n### Installation guide\\n\\n* Install [DevRev CLI](/snapin-development/references/cli-install)\\n* Install [jq](https://stedolan.github.io/jq)\\n* Install [DevRev SDK](https://www.npmjs.com/package/@devrev/typescript-sdk?activeTab=readme)\\n\\n##### \\n\\nIf you did not follow the [getting", - "title": "Snap-in triggered by a DevRev event | DevRev | Docs" + "id": "ART-1274_KNOWLEDGE_NODE-14", + "text": "devrev snap_in_version list |\\n```\\n\\nTo delete the snap-in version, run the following command:\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | devrev snap_in_version delete-one |\\n```\\n\\n[6](/snapin-development/tutorials/getting-started#install-a-snap-in-from-a-snap-in-version)\\n\\n### Install a snap-in from a snap-in version\\n\\nTo create a snap-in from a snap-in version, run the following command:\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | devrev snap_in draft |\\n```\\n\\n##### \\n\\n1. To install the snap-in,", + "title": "Getting started | DevRev | Docs" }, { - "id": "ART-1483_KNOWLEDGE_NODE-30", - "text": "Status](https://devrev.ai/status)\\n\\n\\xc2\\xa9 2025 DevRev Inc.\\n\\n[](https://devrev.ai)\\n\\n * Product\\n * Platform\\n * Solutions\\n * Marketplace\\n * Company\\n * Resources\\n * [Pricing](https://devrev.ai/pricing)\\n\\n __\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](https://devrev.ai/request-a-demo)\\n\\n[](https://devrev.ai)\\n\\n __\\n\\nProduct __\\n\\nPlatform __\\n\\nSolutions __\\n\\nMarketplace __\\n\\nCompany __\\n\\nResources", - "title": "Using a snap-in to perform a DevRev action \u2014 DevRev | Docs" + "id": "ART-1273_KNOWLEDGE_NODE-0", + "text": "b'Overview | DevRev | Docs\\n\\n[![]()![]()](https://developer.devrev.ai/)\\n\\nPublic\\n\\nPublic\\n\\nSearch\\n\\n`/`\\n\\n[Snap-in development](/snapin-development/concepts)[Tutorials](/snapin-development/tutorials/overview)\\n\\nOverview\\n========\\n\\nCopy page\\n\\nThe following tutorials provide a step-by-step guide to creating snap-ins:\\n\\n1. [Getting started](/snapin-development/tutorials/getting-started)\\n2. [Using a snap-in to perform a DevRev", + "title": "Overview | DevRev | Docs" }, { - "id": "ART-1277_KNOWLEDGE_NODE-0", - "text": "b'Snap-in triggered by a DevRev event | DevRev | Docs\\n\\n[![]()![]()](https://developer.devrev.ai/)\\n\\nPublic\\n\\nPublic\\n\\nSearch\\n\\n`/`\\n\\nOn this page\\n\\n* [Introduction](/snapin-development/tutorials/triggered-event#introduction)\\n* [Background context](/snapin-development/tutorials/triggered-event#background-context)\\n* [Resources](/snapin-development/tutorials/triggered-event#resources)\\n\\n[Snap-in", - "title": "Snap-in triggered by a DevRev event | DevRev | Docs" + "id": "ART-1991_KNOWLEDGE_NODE-25", + "text": "helps you bring data from external sources to DevRev and keep them in sync.\\n\\nWhile numerous snap-ins are available and more are in development, you can create your own using [DevRev APIs](https://developer.devrev.ai/).\\n\\nSupport\\n-------\\n\\n| Automate | Integrate | AirSync |\\n| --- | --- | --- |\\n| [Auto parts to conversation](/docs/automations/auto-parts) | [Calendly](/docs/integrations/calendly) | [Salesforce](/docs/integrations/salesforce) |\\n| [Auto-reply](/docs/automations/auto-reply) |", + "title": "Support snap-ins | Computer for Support Teams | DevRev" } ] }, @@ -1684,29 +1684,24 @@ "query": "generate support tickets from slack messages with questions", "retrievals": [ { - "id": "ART-1968_KNOWLEDGE_NODE-13", - "text": "creator](/docs/automations/smart-issue-creator)\\n - [Set user preference for group](/docs/automations/set-user-preference)\\n - [SLA status change Slack notifier](/docs/automations/sla-change-notifier)\\n - [Slash commands](/docs/automations/slash-commands)\\n - [Spam Shield](/docs/automations/spam-shield)\\n - [Subtype Migration](/docs/automations/subtype-migration)\\n - [Ticket age in engineering](/docs/automations/ticket-age-in-engineering)\\n - [Ticket issue field", - "title": "Conversation insights | Support analytics | Computer for Support Teams | DevRev" - }, - { - "id": "ART-4199_KNOWLEDGE_NODE-5", - "text": "ticket conversion](/docs/product/conversation-ticket)\\n + [Tickets](/docs/product/tickets)\\n + [Routing](/docs/product/routing)\\n + [Support best practices](/docs/product/support-bp)\\n + [Customer portal](/docs/product/support-portal)\\n + [Questions & answers](/docs/product/qa)\\n + [Knowledge Base](/docs/product/knowledge-base)\\n\\n - [Articles](/docs/product/articles)\\n - [Collections](/docs/product/collection)\\n + [Turing AI agent](/docs/product/conversational-bot)\\n\\n - [Best", - "title": "Slack message agent | Automate | Snap-ins | DevRev" + "id": "ART-2035_KNOWLEDGE_NODE-37", + "text": "synchronized between DevRev and Slack.\\n\\nWork management using Slack\\n---------------------------\\n\\n### DevRev Tickets and Slack\\n\\nThe Slack snap-in allows users to create tickets directly from Slack. There are multiple ways to initiate ticket creation from any channel:\\n\\n* **Use the command:** Run /devrev create-ticket.\\n* **Message action:** Select **Create a new ticket** from the message actions.\\n* **Convert a Conversation:** Transform an ongoing conversation into a ticket. This is", + "title": "Slack | Integrate | Snap-ins | DevRev" }, { - "id": "ART-15716_KNOWLEDGE_NODE-7", - "text": "Tickets from Chat ConversationsYes, you can create a ticket from a conversation without leaving the chat. Some fields may be prefilled from the conversation.\\n\\nDetails:\\xc2\\xa0[Conv \\xe2\\x86\\x92 Ticket Creation](https://devrev.ai/docs/product/conversation-ticket)\\n\\n5. Viewing Ticket Activity to Avoid Duplicate Responses\\n\\nCurrently, there\\xe2\\x80\\x99s no direct feature to see who is viewing a ticket in real time. But, we can see if someone is typing on a ticket.\\n\\n6. Generating AI Summaries", - "title": "Support queries related playbook" + "id": "ART-4271_KNOWLEDGE_NODE-24", + "text": "[Support](/docs/product/support?)\\n 4. [Conversations](/docs/product/conversation?)\\n 5. [Convert Conversations to Tickets](/docs/product/Conversation-Tickets?)\\n\\n# Convert Conversations to Tickets\\n\\nYou can now convert conversations from PLuG and Slack directly into tickets. Previously, conversations were only linked to tickets. This update streamlines workflows and enhances the customer experience.\\n\\nFor conversations originating from PLuG or Slack, the **Link to Ticket** functionality", + "title": "Convert Conversations to Tickets | Conversations | Support | DevRev" }, { - "id": "ART-1983_KNOWLEDGE_NODE-13", - "text": "group](/docs/automations/set-user-preference)\\n - [SLA status change Slack notifier](/docs/automations/sla-change-notifier)\\n - [Slash commands](/docs/automations/slash-commands)\\n - [Spam Shield](/docs/automations/spam-shield)\\n - [Subtype Migration](/docs/automations/subtype-migration)\\n - [Ticket age in engineering](/docs/automations/ticket-age-in-engineering)\\n - [Ticket issue field migrator](/docs/automations/ticket-issue-field-migrator)\\n - [Ticket", - "title": "Questions & answers | Computer for Support Teams | DevRev" + "id": "ART-17515_KNOWLEDGE_NODE-26", + "text": "and feature requests on tickets.\\n* Computer on Plug: Enhances the following functionalities:\\n\\n + Conversation: It deflects customer queries using your knowledge base, providing accurate and relevant responses.\\n + Search: It summarizes your search results, making information retrieval more efficient and user-friendly.\\n* Computer assist: Recommends relevant articles and similar work items.\\n* Slack tickets: Automatically generates titles and descriptions for tickets created from Slack", + "title": "AI use cases in DevRev | Computer by DevRev | DevRev" }, { - "id": "ART-1983_KNOWLEDGE_NODE-5", - "text": "ticket conversion](/docs/product/conversation-ticket)\\n + [Tickets](/docs/product/tickets)\\n + [Routing](/docs/product/routing)\\n + [Support best practices](/docs/product/support-bp)\\n + [Customer portal](/docs/product/support-portal)\\n + [Questions & answers](/docs/product/qa)\\n + [Knowledge Base](/docs/product/knowledge-base)\\n\\n - [Articles](/docs/product/articles)\\n - [Collections](/docs/product/collection)\\n + [Turing AI agent](/docs/product/conversational-bot)\\n\\n - [Best", - "title": "Questions & answers | Computer for Support Teams | DevRev" + "id": "ART-2035_KNOWLEDGE_NODE-44", + "text": "directly from Slack:\\n\\n* Using the /devrev create-issue command.\\n* Using the **Create a new issue** message action.\\n\\nBoth the options open a new pop-up modal with a new issue form. Some of the fields are pre-populated based on the messages in the thread.\\n\\n* The **Share with everyone** functionality operates identically to ticket creation. Only shared issues are synchronized between the platforms.\\n* The messages are always synced in the **Internal Discussions** panel with Slack thread.\\n*", + "title": "Slack | Integrate | Snap-ins | DevRev" }, { "id": "ART-6174_KNOWLEDGE_NODE-30", @@ -1714,24 +1709,29 @@ "title": "Conversation to ticket conversion | Conversations | Computer for Support Teams | DevRev" }, { - "id": "ART-6174_KNOWLEDGE_NODE-13", - "text": "creator](/docs/automations/smart-issue-creator)\\n - [Set user preference for group](/docs/automations/set-user-preference)\\n - [SLA status change Slack notifier](/docs/automations/sla-change-notifier)\\n - [Slash commands](/docs/automations/slash-commands)\\n - [Spam Shield](/docs/automations/spam-shield)\\n - [Subtype Migration](/docs/automations/subtype-migration)\\n - [Ticket age in engineering](/docs/automations/ticket-age-in-engineering)\\n - [Ticket issue field", - "title": "Conversation to ticket conversion | Conversations | Computer for Support Teams | DevRev" + "id": "ART-2035_KNOWLEDGE_NODE-39", + "text": "fields will auto-fill based on the messages.\\n\\n### Ticket sharing options\\n\\nThe new ticket modal in Slack includes a **Share with everyone** checkbox at the bottom:\\n\\n* **Enabled:** Shares the ticket details with the Slack channel via a summary card.\\n* **Disabled:** Keeps the ticket internal with no updates to the Slack channel.\\n\\nRegardless of sharing, the ticket details are visible to the creator in the submission modal.\\n\\n### Syncing details\\n\\nIf sharing is enabled, the type of Slack", + "title": "Slack | Integrate | Snap-ins | DevRev" }, { - "id": "ART-4021_KNOWLEDGE_NODE-5", - "text": "ticket conversion](/docs/product/conversation-ticket)\\n + [Tickets](/docs/product/tickets)\\n + [Routing](/docs/product/routing)\\n + [Support best practices](/docs/product/support-bp)\\n + [Customer portal](/docs/product/support-portal)\\n + [Questions & answers](/docs/product/qa)\\n + [Knowledge Base](/docs/product/knowledge-base)\\n\\n - [Articles](/docs/product/articles)\\n - [Collections](/docs/product/collection)\\n + [Turing AI agent](/docs/product/conversational-bot)\\n\\n - [Best", - "title": "Slack scraper | Automate | Snap-ins | DevRev" + "id": "ART-4965_KNOWLEDGE_NODE-15", + "text": "[Custom field migration](/docs/automations/custom-field-migration)\\n - [Slack scraper](/docs/automations/slack-scraper)\\n - [Slack Broadcaster](/docs/automations/slack-broadcaster)\\n - [Reported by enricher](/docs/automations/ticket-reported-by)\\n - [Ticket approval workflow](/docs/automations/ticket-approval-workflow)\\n - [Ticket linked issues comment sync](/docs/automations/ticket-linked-issues-comment-sync)\\n - [Slack message agent](/docs/automations/slack-message-agent)\\n", + "title": "Ticket Immutability | Automate | Snap-ins | DevRev" }, { - "id": "ART-1991_KNOWLEDGE_NODE-5", - "text": "ticket conversion](/docs/product/conversation-ticket)\\n + [Tickets](/docs/product/tickets)\\n + [Routing](/docs/product/routing)\\n + [Support best practices](/docs/product/support-bp)\\n + [Customer portal](/docs/product/support-portal)\\n + [Questions & answers](/docs/product/qa)\\n + [Knowledge Base](/docs/product/knowledge-base)\\n\\n - [Articles](/docs/product/articles)\\n - [Collections](/docs/product/collection)\\n + [Turing AI agent](/docs/product/conversational-bot)\\n\\n - [Best", - "title": "Support snap-ins | Computer for Support Teams | DevRev" + "id": "ART-12395_KNOWLEDGE_NODE-15", + "text": "[Custom field migration](/docs/automations/custom-field-migration)\\n - [Slack scraper](/docs/automations/slack-scraper)\\n - [Slack Broadcaster](/docs/automations/slack-broadcaster)\\n - [Reported by enricher](/docs/automations/ticket-reported-by)\\n - [Ticket approval workflow](/docs/automations/ticket-approval-workflow)\\n - [Ticket linked issues comment sync](/docs/automations/ticket-linked-issues-comment-sync)\\n - [Slack message agent](/docs/automations/slack-message-agent)\\n", + "title": "Slack Broadcaster | Automate | Snap-ins | DevRev" + }, + { + "id": "ART-4218_KNOWLEDGE_NODE-15", + "text": "[Custom field migration](/docs/automations/custom-field-migration)\\n - [Slack scraper](/docs/automations/slack-scraper)\\n - [Slack Broadcaster](/docs/automations/slack-broadcaster)\\n - [Reported by enricher](/docs/automations/ticket-reported-by)\\n - [Ticket approval workflow](/docs/automations/ticket-approval-workflow)\\n - [Ticket linked issues comment sync](/docs/automations/ticket-linked-issues-comment-sync)\\n - [Slack message agent](/docs/automations/slack-message-agent)\\n", + "title": "Azure DevOps Wikis AirSync | AirSync | Snap-ins | DevRev" }, { - "id": "ART-1973_KNOWLEDGE_NODE-13", - "text": "creator](/docs/automations/smart-issue-creator)\\n - [Set user preference for group](/docs/automations/set-user-preference)\\n - [SLA status change Slack notifier](/docs/automations/sla-change-notifier)\\n - [Slash commands](/docs/automations/slash-commands)\\n - [Spam Shield](/docs/automations/spam-shield)\\n - [Subtype Migration](/docs/automations/subtype-migration)\\n - [Ticket age in engineering](/docs/automations/ticket-age-in-engineering)\\n - [Ticket issue field", - "title": "Conversation-SLA Analytics | Support analytics | Computer for Support Teams | DevRev" + "id": "ART-2037_KNOWLEDGE_NODE-15", + "text": "[Custom field migration](/docs/automations/custom-field-migration)\\n - [Slack scraper](/docs/automations/slack-scraper)\\n - [Slack Broadcaster](/docs/automations/slack-broadcaster)\\n - [Reported by enricher](/docs/automations/ticket-reported-by)\\n - [Ticket approval workflow](/docs/automations/ticket-approval-workflow)\\n - [Ticket linked issues comment sync](/docs/automations/ticket-linked-issues-comment-sync)\\n - [Slack message agent](/docs/automations/slack-message-agent)\\n", + "title": "GitHub | Integrate | Snap-ins | DevRev" } ] }, @@ -1739,55 +1739,55 @@ "query_id": "2e98cdf9-4951-4185-a63a-295def43b837", "query": "cron configuration for timer trigger schedule in DevRev", "retrievals": [ - { - "id": "ART-1275_KNOWLEDGE_NODE-8", - "text": "type `cron` or\\n`interval_seconds` as mentioned in the\\n[documentation](/snapin-development/references/event-sources#timer-based-event-sources).\\nThe `cron` config is used here.\\n\\nmanifest.yaml\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | event_sources: |\\n| 2 | organization: |\\n| 3 | - name: timer-event-source |\\n| 4 | description: Event source that sends events every 10 minutes. |\\n| 5 | display_name: Timer Event Source |\\n| 6 | type: timer-events |\\n| 7 | config: |\\n| 8 | # CRON expression for", - "title": "Using a snap-in to perform a DevRev action | DevRev | Docs" - }, { "id": "ART-1483_KNOWLEDGE_NODE-11", - "text": "config: \\n 8| # CRON expression for triggering every 10 minutes. \\n 9| cron: \"*/10 * * * *\" \\n 10| metadata: \\n 11| event_key: ten_minute_event\\n[/code] \\n \\nFinally, update the `function` name to better reflect the behavior and `automation`name to use the event type corresponding to the `timer-events` event source.\\n\\nmanifest.yaml\\n\\n[code]\\n\\n 1| functions: \\n ---|--- \\n 2| - name: ticket_creator \\n 3|", + "text": "config: \\n 8| # CRON expression for triggering every 10 minutes. \\n 9| cron: \"*/10 * * * *\" \\n 10| metadata: \\n 11| event_key: ten_minute_event\\n[/code] \\n \\nFinally, update the `function` name to better reflect the behavior and `automation`name to use the event type corresponding to the `timer-events` event source.\\n\\nmanifest.yaml\\n\\n[code]\\n\\n 1| functions: \\n ---|--- \\n 2| - name: ticket_creator \\n 3|", "title": "Using a snap-in to perform a DevRev action \u2014 DevRev | Docs" }, { - "id": "ART-1483_KNOWLEDGE_NODE-10", - "text": "`interval_seconds` as mentioned in the [documentation](/public/snapin-development/references/event-sources#timer-based-event-sources). The `cron` config is used here.\\n\\nmanifest.yaml\\n\\n[code]\\n\\n 1| event_sources: \\n ---|--- \\n 2| organization: \\n 3| - name: timer-event-source \\n 4| description: Event source that sends events every 10 minutes. \\n 5| display_name: Timer Event Source \\n 6| type: timer-events \\n 7|", - "title": "Using a snap-in to perform a DevRev action \u2014 DevRev | Docs" + "id": "ART-1478_KNOWLEDGE_NODE-42", + "text": "source configuration.\\n\\n[code]\\n\\n 1| event_sources: \\n ---|--- \\n 2| organization: \\n 3| - name: daily-timer-source \\n 4| description: Timer event source based on Cron expression \\n 5| display_name: Timer source \\n 6| type: timer-events \\n 7| config: \\n 8| cron: \"0 0 * * *\" \\n 9| metadata: \\n 10| event_key: daily_events \\n 11| \\n 12| - name: hourly-events \\n 13|", + "title": "Event sources \u2014 DevRev | Docs" }, { - "id": "ART-1275_KNOWLEDGE_NODE-9", - "text": "triggering every 10 minutes. |\\n| 9 | cron: \"*/10 * * * *\" |\\n| 10 | metadata: |\\n| 11 | event_key: ten_minute_event |\\n```\\n\\nFinally, update the `function` name to better reflect the behavior and\\n`automation`name to use the event type corresponding to the `timer-events` event\\nsource.\\n\\nmanifest.yaml\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | functions: |\\n| 2 | - name: ticket_creator |\\n| 3 | description: Function to create a new ticket when triggered. |\\n| 4 | |\\n| 5 | automations: |\\n| 6 | -", + "id": "ART-1284_KNOWLEDGE_NODE-37", + "text": "configuration.\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | event_sources: |\\n| 2 | organization: |\\n| 3 | - name: daily-timer-source |\\n| 4 | description: Timer event source based on Cron expression |\\n| 5 | display_name: Timer source |\\n| 6 | type: timer-events |\\n| 7 | config: |\\n| 8 | cron: \"0 0 * * *\" |\\n| 9 | metadata: |\\n| 10 | event_key: daily_events |\\n| 11 | |\\n| 12 | - name: hourly-events |\\n| 13 | description: Timer event source based on interval seconds |\\n| 14 | display_name: Timer", + "title": "Event sources | DevRev | Docs" + }, + { + "id": "ART-1275_KNOWLEDGE_NODE-8", + "text": "type `cron` or\\n`interval_seconds` as mentioned in the\\n[documentation](/snapin-development/references/event-sources#timer-based-event-sources).\\nThe `cron` config is used here.\\n\\nmanifest.yaml\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | event_sources: |\\n| 2 | organization: |\\n| 3 | - name: timer-event-source |\\n| 4 | description: Event source that sends events every 10 minutes. |\\n| 5 | display_name: Timer Event Source |\\n| 6 | type: timer-events |\\n| 7 | config: |\\n| 8 | # CRON expression for", "title": "Using a snap-in to perform a DevRev action | DevRev | Docs" }, { - "id": "ART-4257_KNOWLEDGE_NODE-23", - "text": "the time spent on specific tasks, allowing you to track events such as response time, loading time, or any other duration-based metrics.\\n\\nThe mechanism utilizes balanced start and stop methods, both of which accept a timer name and an optional dictionary of properties.\\n\\nTo start a timer, use the following method:\\n\\n[code]\\n\\n 1| DevRev.startTimer(_:properties:) \\n ---|---\\n[/code] \\n \\nTo stop a timer, use the following method:\\n\\n[code]\\n\\n 1| DevRev.stopTimer(_:properties:)", - "title": "DevRev SDK for iOS \u2014 DevRev | Docs" + "id": "ART-1275_KNOWLEDGE_NODE-5", + "text": "devrev snap_in_version init |\\n```\\n\\n#### Trigger\\n\\nThe trigger condition for the snap-in is dictated by the\\n[Event Sources](/snapin-development/references/event-sources)\\nsection in the manifest. The [`timer-events`](/snapin-development/references/event-sources#timer-based-event-sources)\\nevent source is suitable for the use-case, since it allows trigger of snap-ins\\nusing [CRON expression](https://crontab.guru/).\\n\\n#### Action\\n\\nThe hello-world snap-in prints a log message whenever the", + "title": "Using a snap-in to perform a DevRev action | DevRev | Docs" }, { - "id": "ART-1483_KNOWLEDGE_NODE-9", - "text": "better reflect the snap-in\\xe2\\x80\\x99s behavior.\\n\\nmanifest.yaml\\n\\n[code]\\n\\n 1| version: \"2\" \\n ---|--- \\n 2| \\n 3| name: \"Timely Ticketer\" \\n 4| description: \"Snap-in to create ticket every 10 minutes\" \\n 5| \\n 6| service_account: \\n 7| display_name: Automatic Ticket Creator Bot\\n[/code] \\n \\nNext, update the `event_sources` section to use the `timer-events` event source. The `timer-events` source type takes a `config` of type `cron` or", + "id": "ART-1483_KNOWLEDGE_NODE-10", + "text": "`interval_seconds` as mentioned in the [documentation](/public/snapin-development/references/event-sources#timer-based-event-sources). The `cron` config is used here.\\n\\nmanifest.yaml\\n\\n[code]\\n\\n 1| event_sources: \\n ---|--- \\n 2| organization: \\n 3| - name: timer-event-source \\n 4| description: Event source that sends events every 10 minutes. \\n 5| display_name: Timer Event Source \\n 6| type: timer-events \\n 7|", "title": "Using a snap-in to perform a DevRev action \u2014 DevRev | Docs" }, { - "id": "ART-15417_KNOWLEDGE_NODE-8", - "text": "with](https://buildwithfern.com/?utm_campaign=buildWith&utm_medium=docs&utm_source=developer.devrev.ai)'", - "title": "Create Org Schedule | DevRev | Docs" + "id": "ART-1275_KNOWLEDGE_NODE-9", + "text": "triggering every 10 minutes. |\\n| 9 | cron: \"*/10 * * * *\" |\\n| 10 | metadata: |\\n| 11 | event_key: ten_minute_event |\\n```\\n\\nFinally, update the `function` name to better reflect the behavior and\\n`automation`name to use the event type corresponding to the `timer-events` event\\nsource.\\n\\nmanifest.yaml\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | functions: |\\n| 2 | - name: ticket_creator |\\n| 3 | description: Function to create a new ticket when triggered. |\\n| 4 | |\\n| 5 | automations: |\\n| 6 | -", + "title": "Using a snap-in to perform a DevRev action | DevRev | Docs" }, { - "id": "ART-12456_KNOWLEDGE_NODE-19", - "text": "you can use the following method:\\n\\n[code]\\n\\n 1| DevRev.unmarkSensitiveViews(tags: any[]) \\n ---|---\\n[/code] \\n \\n### Timers\\n\\nThe DevRev SDK offers a timer mechanism to measure the time spent on specific tasks, allowing you to track events such as response time, loading time, or any other duration-based metrics.\\n\\nThe mechanism uses balanced start and stop methods, both of which accept a timer name and an optional dictionary of properties.\\n\\nTo start a timer, use the following", + "id": "ART-12449_KNOWLEDGE_NODE-33", + "text": "type=\"text\" placeholder=\"Enter Username\" name=\"username\" required class=\"devrev-unmask\"> \\n ---|---\\n[/code] \\n \\n### Timers\\n\\nThe DevRev SDK offers a timer mechanism to measure the time spent on specific tasks, allowing you to track events such as response time, loading time, or any other duration-based metrics.\\n\\nThe mechanism works using balanced start and stop methods that both accept a timer name and an optional dictionary of properties.\\n\\nTo start a timer, use the following", "title": "Features \u2014 DevRev | Docs" }, { - "id": "ART-15434_KNOWLEDGE_NODE-8", - "text": "with](https://buildwithfern.com/?utm_campaign=buildWith&utm_medium=docs&utm_source=developer.devrev.ai)'", - "title": "Update Org Schedule | DevRev | Docs" + "id": "ART-1485_KNOWLEDGE_NODE-8", + "text": "comment to the object timeline.\\n\\nTo learn more, refer to the [Using a snap-in to perform a DevRev action](/public/snapin-development/tutorials/timer-ticket-creator) tutorial.\\n\\n[1](/public/snapin-development/tutorials/triggered-event#installation-guide)\\n\\n### Installation guide\\n\\n * Install [DevRev CLI](/public/snapin-development/references/cli-install)\\n * Install [jq](https://stedolan.github.io/jq)\\n * Install [DevRev", + "title": "Snap-in triggered by a DevRev event \u2014 DevRev | Docs" }, { - "id": "ART-4255_KNOWLEDGE_NODE-21", - "text": "to measure the time spent on specific tasks, allowing you to track events such as response time, loading time, or any other duration-based metrics.\\n\\nThe mechanism utilizes balanced start and stop methods, both of which accept a timer name and an optional hashmap of properties.\\n\\nTo start a timer, use the following method:\\n\\n###### Kotlin\\n\\n###### Java\\n\\n[code]\\n\\n 1| DevRev.startTimer(name: String, properties: HashMap) \\n ---|---\\n[/code] \\n \\nTo stop a timer, use", - "title": "DevRev SDK for Android \u2014 DevRev | Docs" + "id": "ART-1277_KNOWLEDGE_NODE-4", + "text": "[Using a snap-in to perform a DevRev action](/snapin-development/tutorials/timer-ticket-creator) tutorial.\\n\\n[1](/snapin-development/tutorials/triggered-event#installation-guide)\\n\\n### Installation guide\\n\\n* Install [DevRev CLI](/snapin-development/references/cli-install)\\n* Install [jq](https://stedolan.github.io/jq)\\n* Install [DevRev SDK](https://www.npmjs.com/package/@devrev/typescript-sdk?activeTab=readme)\\n\\n##### \\n\\nIf you did not follow the [getting", + "title": "Snap-in triggered by a DevRev event | DevRev | Docs" } ] }, @@ -1796,54 +1796,54 @@ "query": "view all tickets raised to DevRev support team", "retrievals": [ { - "id": "ART-1979_KNOWLEDGE_NODE-27", - "text": "also be used to engage customers for feedback/ideas (such as new feature ideas). Scoping is important for broadcast tickets as there needs to be a differentiation between broadcast (all revs) vs. multicast (particular revs).\\n\\nViews of tickets can be found under **Support** in the DevRev app.\\n\\n![]()\\n\\nYou can export views to CSV or JSON by selecting **Actions** in the upper-right corner and choosing the format.\\n\\nAttributes\\n----------\\n\\nTickets have attributes that can be used to filter", - "title": "Tickets | Computer for Support Teams | DevRev" + "id": "ART-2046_KNOWLEDGE_NODE-29", + "text": "Ticket** button to create a ticket in DevRev by filling necessary attributes. You can turn this feature off in the app configuration if you want.\\n* To view comments on the tickets linked to the discussions that support teams had with customers or internally on DevRev, head over to the DevRev activity tab which is present in the same line as the **Comments** tab of Jira.\\n* To send comments from the Jira issue to the DevRev ticket, select the ticket from the dropdown, type in the comment, and", + "title": "DevRev for Jira app | Jira Software AirSync | AirSync | Snap-ins | DevRev" }, { - "id": "ART-1979_KNOWLEDGE_NODE-37", - "text": "filters and **Group** conditions across various vistas in DevRev to track specific work, capacity, and more.\\n\\nYou can add custom attributes to tickets to track additional information. For more information on custom attributes, see [object customization](./object-customization).\\n\\nIssues are attached to tickets in order to track efforts with product priorities.\\n\\nCreate a ticket\\n---------------\\n\\n1. Go to **Support** > **Tickets** from the sidebar on the left.\\n2. Click **New Ticket** on", - "title": "Tickets | Computer for Support Teams | DevRev" + "id": "ART-1978_KNOWLEDGE_NODE-33", + "text": "tickets but also all the tickets raised by the other users from their organization. You can add multiple customer admins from the same customer organization.\\n\\nOnly verified users can login into the portal.\\n\\nTo create a verified user:\\n\\n1. Go to **Accounts** in the DevRev app and create an account.\\n2. Create a contact under **Contacts** and link it to the account.\\n\\n### Set up customer admins\\n\\nTo set up customer admins, follow these steps:\\n\\n1. Log in on your DevRev app with your", + "title": "Customer portal | Computer for Support Teams | DevRev" }, { - "id": "ART-1979_KNOWLEDGE_NODE-40", - "text": "a child issue or create a new one by clicking on **+ New issue**.\\nJust update the title of the child issue and click enter. All other fields will be populated automatically by DevRev. You can edit them later.\\n\\nTags\\n----\\n\\n* Stalled\\n* Priority/Escalated\\n* Fast/Slow Moving\\n* Blocked\\n* Resolution: [*value*]\\n* Impact: [*value*]\\n* Reason: [*value*]\\n\\nStages\\n------\\n\\nThe following figure shows the state machine for tickets.\\n\\n```\\nClosed\\n\\n\\n\\nIn", - "title": "Tickets | Computer for Support Teams | DevRev" + "id": "ART-1978_KNOWLEDGE_NODE-44", + "text": "URL and not on the support portal of some other customer.\\n* Customer admin isn't able to see all the tickets of the organization.\\n\\n + This could happen if the customer isn't logged in on the correct URL. If the customer is logged in on the correct URL, then check if there are any tickets that are reported by the other customers in that organization or not. Check if the customer is added as a customer admin or not by logging in to your DevRev application.\\n* You are not able to add customer", + "title": "Customer portal | Computer for Support Teams | DevRev" }, { - "id": "ART-1979_KNOWLEDGE_NODE-35", - "text": "docs](https://docs.devrev.ai/import).\\n* **Close date**: The date the ticket was closed.\\n* **Source channel**: The channel through which the ticket was created. Customers can create tickets via email, the portal, and various other channels.\\n* **Channel**: Indicates the medium used for customer communication.\\n* **Subscribers**: Indicates the group of users who will receive updates about the tickets.External contacts cannot be added as subscribers, so a [DevRev", - "title": "Tickets | Computer for Support Teams | DevRev" + "id": "ART-1978_KNOWLEDGE_NODE-43", + "text": "with that email or not.\\n + This could also be because your customer hasn't logged in.\\n* Customer isn't able to view the tickets they have created.\\n\\n + Check if there are any reported tickets by that customer. You can do so by logging into your DevRev app and then going into the tickets section. Here you can filter based on **reported by** and see if any tickets have been reported by the customer who isn't able to view the tickets.\\n + Check if the customer has logged in on the correct", + "title": "Customer portal | Computer for Support Teams | DevRev" }, { - "id": "ART-1979_KNOWLEDGE_NODE-23", - "text": "2025](/docs/changelog/_2025-06-01)\\n + [May 2025](/docs/changelog/_2025-05-01)\\n + [March and April 2025](/docs/changelog/_2025-04-01)\\n + [February 2025](/docs/changelog/_2025-02-01)\\n* [Developer \\xe2\\x86\\x97\\xef\\xb8\\x8f](https://developer.devrev.ai/)\\n* [DevRevU \\xe2\\x86\\x97\\xef\\xb8\\x8f](/docs/DevRevU)\\n\\n + [Product demos](/docs/DevRevU/demos)\\n\\nOn this page\\n\\n* [Attributes](#attributes)\\n* [Create a ticket](#create-a-ticket)\\n* [Tags](#tags)\\n* [Stages](#stages)\\n*", + "id": "ART-1979_KNOWLEDGE_NODE-0", + "text": "b\"Tickets | Computer for Support Teams | DevRev\\n\\n* Computer\\n* Resources\\n* [Our Customers](/case-study)\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](/request-a-demo)\\n\\nComputer\\n\\nResources\\n\\n[Our Customers](/case-study)\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](/request-a-demo)\\n\\nSearch\\n\\n`CTRL`\\xc2\\xa0+\\xc2\\xa0`K`\\n\\n* [Introduction](/docs)\\n* [Computer by DevRev](/docs/intro)\\n\\n + [Core concepts](/docs/product/core)\\n + [Apps](/docs/product/apps)\\n +", "title": "Tickets | Computer for Support Teams | DevRev" }, { - "id": "ART-1979_KNOWLEDGE_NODE-25", - "text": "Teams](/docs/product/support)\\n[Tickets](/docs/product/tickets)\\n\\nTickets\\n=======\\n\\nA *ticket* is a record of a customer's request for assistance or support. When a customer contacts a company with a problem or issue, the company creates a ticket to track the request and ensure that it's addressed in a timely and satisfactory manner. For example, if a user calls in and files a ticket for a problem they're facing any progress would be communicated to them through the ticket.\\n\\nTickets are", - "title": "Tickets | Computer for Support Teams | DevRev" + "id": "ART-1954_KNOWLEDGE_NODE-25", + "text": "DevRev](/docs/intro)\\n[Updates](/docs/product/updates)\\n\\nUpdates\\n=======\\n\\nUpdates help you stay on top of all your activity on DevRev.\\n\\nConversations, tickets, and issues where you are an owner, member, or creator, or where comments are made or you are @mentioned, are automatically shown in your updates. A group can also be mentioned here which will send a notification to all the members of the group. For other tickets and issues, you can follow them to receive some or all updates through", + "title": "Updates | Computer by DevRev | DevRev" }, { - "id": "ART-1242_KNOWLEDGE_NODE-1", - "text": "about work items, refer to [Tickets](https://docs.devrev.ai/product/tickets) and [Issues](https://docs.devrev.ai/product/issues).\\n\\nWas this page helpful?\\n\\nYesNo\\n\\n[Previous](/api-reference/webhooks/update)[#### Create Work\\n\\nNext](/api-reference/works/create)[Built with](https://buildwithfern.com/?utm_campaign=buildWith&utm_medium=docs&utm_source=developer.devrev.ai)'", - "title": "Tickets and issues | DevRev | Docs" + "id": "ART-3207_KNOWLEDGE_NODE-47", + "text": "**Primary Use Case** is **Tickets**, go to **Support** > **Tickets** in the DevRev app; otherwise, if the **Primary Use Case** is **Conversation** go to **Inbox**. Find and open your verification message here.\\n6. Open the given link to confirm the request. Make sure you click the link that allows your support address to be forwarded to v\\\\_\\\\_\\\\_\\\\_\\\\_\\\\_\\\\_\\\\_\\\\_\\\\_\\\\_@hooks.devrev.ai.\\n7. Go back to your Gmail forwarding settings, select **Forward a copy of incoming mail** and **Save", + "title": "Email snap-in configuration | Email | Integrate | Snap-ins | DevRev" }, { - "id": "ART-1447_KNOWLEDGE_NODE-1", - "text": "[Tickets](https://docs.devrev.ai/product/tickets) and [Issues](https://docs.devrev.ai/product/issues).\\n\\nWas this page helpful?YesNo\\n\\n[Create WorkUp Next](/public/api-reference/works/create)\\n\\n[Built with](https://buildwithfern.com/?utm_campaign=buildWith&utm_medium=docs&utm_source=developer.devrev.ai)\\n\\n[Enterprise grade security to protect customer dataLearn more about it.](https://devrev.ai/blog/soc-compliance)\\n\\nProduct\\n\\n * [Build](https://devrev.ai/build)\\n *", - "title": "Tickets and issues \u2014 DevRev | Docs" + "id": "ART-2027_KNOWLEDGE_NODE-29", + "text": "your communication requirements.\\n\\nThe visibility and interaction capabilities with a ticket in DevRev are determined by the user's role and how they were added to the email thread.\\n\\nEnd users\\n\\n* Original sender\\n\\n *Added to:* **Reported by** or **Email members** field.\\n\\n *Is able to:* View the ticket on the portal and reply via email.\\n* An end user in the same organization\\n\\n *Added to:* **To** or **CC** fields in the email thread; **Reported by** field, **Email members** field,", + "title": "Email | Integrate | Snap-ins | DevRev" }, { - "id": "ART-1979_KNOWLEDGE_NODE-41", - "text": "progress\\n\\n\\n\\nOpen\\n\\n\\n\\nEscalate\\n\\n\\n\\nValidate the fix\\n\\n\\n\\nAdditional detail needed\\n\\n\\n\\nCustomer responds\\n\\n\\n\\nStart\\n\\n\\n\\nFeature request accepted\\n\\n\\n\\nResolved\\n\\n\\n\\nNot valid\\n\\n\\n\\nQueued\\n\\n\\n\\nWork in progress\\n\\n\\n\\nAwaiting product assist\\n\\n\\n\\nAwaiting development\\n\\n\\n\\nAwating customer response\\n\\n\\n\\nIn development\\n\\n\\n\\nAccepted\\n\\n\\n\\nResolved\\n\\n\\n\\nCanceled\\n```\\n\\n**Open**\\n\\n* *Queued* (Q)\\n The initial stage for all tickets. When a new ticket is created,", - "title": "Tickets | Computer for Support Teams | DevRev" + "id": "ART-1028_KNOWLEDGE_NODE-19", + "text": "teams\\n\\nJira bidirectional sync\\n\\nSupport team was able to create Jira tickets directly within DevRev\\n\\n### Related Articles\\n\\n[![]()\\n\\n5 min readLuxCreo boosts operational efficiency and agility with DevRev](/case-study/luxcreo)[![]()\\n\\n5 min readAditya Birla Capital optimizes user experience with DevRev](/case-study/aditya-birla-capital)[![]()\\n\\n4 min readJar improves customer insights and increased conversion rates using DevRev](/case-study/jar)[![]()\\n\\n3 min read ICICI Prudential", + "title": "Uniphore builds a proactive support culture with DevRev" }, { - "id": "ART-1963_KNOWLEDGE_NODE-5", - "text": "ticket conversion](/docs/product/conversation-ticket)\\n + [Tickets](/docs/product/tickets)\\n + [Routing](/docs/product/routing)\\n + [Support best practices](/docs/product/support-bp)\\n + [Customer portal](/docs/product/support-portal)\\n + [Questions & answers](/docs/product/qa)\\n + [Knowledge Base](/docs/product/knowledge-base)\\n\\n - [Articles](/docs/product/articles)\\n - [Collections](/docs/product/collection)\\n + [Turing AI agent](/docs/product/conversational-bot)\\n\\n - [Best", - "title": "Accessing DevRev | Computer by DevRev | DevRev" + "id": "ART-1981_KNOWLEDGE_NODE-26", + "text": "a small number of tags to help categorize tickets. For example, at DevRev we have the following: bug, feature-request, other-request, question, and incident.\\n* Designate one or more customer experience engineers to be on call. Add them to the **Support** group inside **Settings > Groups** and as default owner in the **Support Routing** snap-in. Default owners are notified through email and the DevRev app as soon as a new conversation is started.\\n\\nMonitor the inbox\\n-----------------\\n\\n*", + "title": "Support best practices | Computer for Support Teams | DevRev" } ] }, @@ -1857,49 +1857,49 @@ "title": "Customer portal | Computer for Support Teams | DevRev" }, { - "id": "ART-1978_KNOWLEDGE_NODE-39", - "text": "toggle and craft your own title and description.\\n7. Enable **Public portal** to allow unauthenticated users to view/search public articles.\\n8. Click **Save & publish** to make the changes visible on your portal.\\n\\nIf you want to customize the font color and favicon, contact DevRev support. For favicon customization, an icon in .ico format is needed.\\n\\nCustomize portal URL\\n--------------------\\n\\nBy default, your customer portal is hosted at support.devrev.ai/. The", + "id": "ART-1978_KNOWLEDGE_NODE-37", + "text": "portal\\n-----------------------------\\n\\nYou can customize the look of your support portal to match your branding goals.\\n\\n1. Go to **Settings** > **Plug & Portal** > **Portal Settings**.\\n2. Under **Configuration**, enter your site name and upload your company logo.\\n * (Optional) Enable the footer and add your social media and text links in their respective fields.\\n * (Optional) Enable **Search** to get answers in search results.\\n * (Optional) Enable Plug widget to facilitate", "title": "Customer portal | Computer for Support Teams | DevRev" }, { - "id": "ART-1978_KNOWLEDGE_NODE-37", - "text": "portal\\n-----------------------------\\n\\nYou can customize the look of your support portal to match your branding goals.\\n\\n1. Go to **Settings** > **Plug & Portal** > **Portal Settings**.\\n2. Under **Configuration**, enter your site name and upload your company logo.\\n * (Optional) Enable the footer and add your social media and text links in their respective fields.\\n * (Optional) Enable **Search** to get answers in search results.\\n * (Optional) Enable Plug widget to facilitate", + "id": "ART-1978_KNOWLEDGE_NODE-39", + "text": "toggle and craft your own title and description.\\n7. Enable **Public portal** to allow unauthenticated users to view/search public articles.\\n8. Click **Save & publish** to make the changes visible on your portal.\\n\\nIf you want to customize the font color and favicon, contact DevRev support. For favicon customization, an icon in .ico format is needed.\\n\\nCustomize portal URL\\n--------------------\\n\\nBy default, your customer portal is hosted at support.devrev.ai/. The", "title": "Customer portal | Computer for Support Teams | DevRev" }, { - "id": "ART-2063_KNOWLEDGE_NODE-28", - "text": "**Plug Nudges**.\\n2. Click **+ Nudge**.\\n3. In the **Create new nudge** window, select **Banner** and click **Create**.\\n4. In the **Nudge Title** field, enter the nudge name.\\n5. In the **Content** field, enter the nudge title.\\n6. To enable the nudge close button, turn on the **Show a close button** toggle.\\n7. Select the banner color by clicking the color icon.\\n8. Use the **Action** drop-down menu to select the type of engagement you want your users to have when they click the nudge. The", - "title": "Nudges | Computer for Your Customers | DevRev" + "id": "ART-1872_KNOWLEDGE_NODE-1", + "text": "|\\n| > | -H \"Authorization: Bearer \" \\\\ |\\n| > | -d id=id |\\n```\\n\\n[Try it](/beta/api-reference/notifications/content-template-get?explorer=true)\\n\\n200Retrieved\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | { |\\n| 2 | \"content_template\": { |\\n| 3 | \"created_by\": { |\\n| 4 | \"display_id\": \"string\", |\\n| 5 | \"id\": \"string\", |\\n| 6 | \"display_name\": \"string\", |\\n| 7 | \"display_picture\": { |\\n| 8 | \"display_id\": \"string\", |\\n| 9 | \"id\": \"string\", |\\n| 10 | \"file\": { |\\n| 11 | \"type\": \"string\", |\\n|", + "title": "Get Content Template | DevRev | Docs" }, { - "id": "ART-1471_KNOWLEDGE_NODE-16", - "text": "__\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](https://devrev.ai/request-a-demo)\\n\\n[](https://devrev.ai)\\n\\n __\\n\\nProduct __\\n\\nPlatform __\\n\\nSolutions __\\n\\nMarketplace __\\n\\nCompany __\\n\\nResources __\\n\\n[Pricing](https://devrev.ai/pricing)\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](https://devrev.ai/request-a-demo)\\n\\n'", - "title": "Restricted messages on a timeline \u2014 DevRev | Docs" + "id": "ART-15510_KNOWLEDGE_NODE-15", + "text": "`DevRev.stopRecording(successCallback, errorCallback)` | Ends the session recording and uploads it to the portal. |\\n| `DevRev.pauseRecording(successCallback, errorCallback)` | Pauses the ongoing session recording. |\\n| `DevRev.resumeRecording(successCallback, errorCallback)` | Resumes a paused session recording. |\\n\\n### Session properties\\n\\nYou can add custom properties to the session recording to help you understand the context of the session. The properties are defined as a map of string", + "title": "Features | DevRev | Docs" }, { - "id": "ART-982_KNOWLEDGE_NODE-3", - "text": "to show our offer, the image, and action (e.g. launch URL).\\n\\nI\\xe2\\x80\\x99ve configured this and you can check it out HERE!\\n\\nTypes of Nudges\\n\\nDevRev Nudges currently supports two core types of nudges:\\n\\n\\n Banner\\n \\n A banner at the top of the webpage\\n Can only be text\\n Can contain an action on click\\n \\n \\n Spotlight\\n \\n A card located by the PLuG widget\\n Can contain an image\\n Can contain an action on click\\n \\n \\n\\n\\nSee It In", - "title": "DevRev Nudges - Driving Customer Engagement" + "id": "ART-4255_KNOWLEDGE_NODE-19", + "text": "recording.| startRecording()| startRecording(DevRev.INSTANCE, context); \\nEnds the session recording and uploads it to the portal.| stopRecording()| stopRecording(DevRev.INSTANCE); \\nPauses the ongoing session recording.| pauseRecording()| pauseRecording(DevRev.INSTANCE); \\nResumes a paused session recording.| resumeRecording()| resumeRecording(DevRev.INSTANCE); \\n \\n### Session properties\\n\\nYou can add custom properties to the session recording to help you understand the context of the", + "title": "DevRev SDK for Android \u2014 DevRev | Docs" }, { - "id": "ART-10697_KNOWLEDGE_NODE-31", - "text": "boosting engagement and reducing repetitive inquiries. To enable Plug, go to **Settings > Portal Settings**, activate Plug widget, and **Save** and **Publish**.\\n\\n![]()\\xc2\\xa0For more information about *Support App*, refer to the following articles: \\xe2\\x80\\xa3 [Support snap-ins | Support](/docs/product/snapins-support) \\xe2\\x80\\xa3 [Support best practices | Support](/docs/product/support-bp) \\xe2\\x80\\xa3 [Support](/docs/product/support) \\xe2\\x80\\xa3", - "title": "February 2025 | Changelog | DevRev" + "id": "ART-1873_KNOWLEDGE_NODE-1", + "text": "\\\\ |\\n| > | -H \"Authorization: Bearer \" |\\n```\\n\\n[Try it](/beta/api-reference/notifications/content-template-list?explorer=true)\\n\\n200Retrieved\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | { |\\n| 2 | \"content_template\": [ |\\n| 3 | { |\\n| 4 | \"created_by\": { |\\n| 5 | \"display_id\": \"string\", |\\n| 6 | \"id\": \"string\", |\\n| 7 | \"display_name\": \"string\", |\\n| 8 | \"display_picture\": { |\\n| 9 | \"display_id\": \"string\", |\\n| 10 | \"id\": \"string\", |\\n| 11 | \"file\": { |\\n| 12 | \"type\": \"string\", |\\n| 13 |", + "title": "List Content Template | DevRev | Docs" }, { - "id": "ART-886_KNOWLEDGE_NODE-3", - "text": "to show our offer, the image, and action (e.g. launch URL).\\n\\nI\\xe2\\x80\\x99ve configured this and you can check it out HERE!\\n\\nTypes of Nudges\\n\\nDevRev Nudges currently supports two core types of nudges:\\n\\n\\n Banner\\n \\n A banner at the top of the webpage\\n Can only be text\\n Can contain an action on click\\n \\n \\n Spotlight\\n \\n A card located by the PLuG widget\\n Can contain an image\\n Can contain an action on click\\n \\n \\n\\n\\nSee It In", - "title": "Nudges | The Book of DevRev" + "id": "ART-1820_KNOWLEDGE_NODE-1", + "text": "\\\\ |\\n| > | -H \"Authorization: Bearer \" \\\\ |\\n| > | -H \"Content-Type: application/json\" \\\\ |\\n| > | -d \\'{ |\\n| > | \"notifications\": [ |\\n| > | { |\\n| > | \"event_type\": \"alert\", |\\n| > | \"metadata\": [ |\\n| > | { |\\n| > | \"content_template\": \"string\" |\\n| > | } |\\n| > | ] |\\n| > | } |\\n| > | ] |\\n| > | }\\' |\\n```\\n\\n[Try it](/beta/api-reference/notifications/send?explorer=true)\\n\\n200Successful\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | {} |\\n```\\n\\nGenerate a notification.\\n\\n###", + "title": "Send Notifications | DevRev | Docs" }, { - "id": "ART-2059_KNOWLEDGE_NODE-12", - "text": "width=\"0\" style=\"display:none;visibility:hidden\">'", - "title": "Install PLuG chat on your website" + "id": "ART-2982_KNOWLEDGE_NODE-16", + "text": "\\n`DevRev.stopRecording()`| Ends the session recording and uploads it to the portal. \\n`DevRev.pauseRecording()`| Pauses the ongoing session recording. \\n`DevRev.resumeRecording()`| Resumes a paused session recording. \\n \\n### Session properties\\n\\nYou can add custom properties to the session recording to help you understand the context of the session. The properties are defined as a map of string values.\\n\\n[code]\\n\\n 1| DevRev.addSessionProperties(properties: Map) \\n", + "title": "React Native integration \u2014 DevRev | Docs" }, { - "id": "ART-1265_KNOWLEDGE_NODE-0", - "text": "b'Restricted messages on a timeline | DevRev | Docs\\n\\n[![]()![]()](https://developer.devrev.ai/)\\n\\nPublic\\n\\nPublic\\n\\nSearch\\n\\n`/`\\n\\nOn this page\\n\\n* [Introduction](/guides/timeline-entries#introduction)\\n* [Send a restricted visibility message](/guides/timeline-entries#send-a-restricted-visibility-message)\\n* [Summary](/guides/timeline-entries#summary)\\n\\n[Guides](/guides/webhooks)\\n\\nRestricted messages on a timeline\\n=================================\\n\\nCopy", - "title": "Restricted messages on a timeline | DevRev | Docs" + "id": "ART-15716_KNOWLEDGE_NODE-23", + "text": "steps, your customer portal will be accessible at the custom domain you\\'ve chosen.Account and Authentication\\n\\nTroubleshooting Sign-Up Issues\\n\\nIf a user can\\xe2\\x80\\x99t sign up:\\n\\nConfirm which signup method they\\xe2\\x80\\x99re using (email, SSO, etc.).\\n\\nCheck if they\\xe2\\x80\\x99re seeing an error message\\xe2\\x80\\x94if so, note the exact wording.\\n\\nCommon blockers include: email already in use, password policy issues, or incomplete form fields.\\n\\nIf the issue persists after retrying,", + "title": "Support queries related playbook" } ] }, @@ -1908,8 +1908,13 @@ "query": "sync contacts and accounts from DevRev to Salesforce", "retrievals": [ { - "id": "ART-2047_KNOWLEDGE_NODE-35", - "text": "longer available.\\n\\n### Sync to DevRev\\n\\nAfter a successful import from a Salesforce account, you can choose to sync the imported data with DevRev. This feature airdrops any new items and any changes made to previously imported items from Salesforce.\\n\\nTo perform a one-time sync to DevRev, follow these steps:\\n\\n1. Go to **Settings** > **Integrations** > **AirSyncs**.\\n2. Locate the previously imported project.\\n3. Select **\\xe2\\x8b\\xae** > **Sync Salesforce Service to", + "id": "ART-15716_KNOWLEDGE_NODE-2", + "text": "details](https://devrev.ai/docs/integrations/jira)\\n\\n4. Integration with Salesforce\\n\\nYes, DevRev offers a Salesforce integration. You can sync accounts, contacts, opportunities, and more between DevRev and Salesforce.\\n\\n[Salesforce integration overview](https://devrev.ai/docs/integrations/salesforce)\\n\\n5. Configuring Email Integration Snap-In\\n\\nGo to Settings \\xe2\\x86\\x92 Integrations \\xe2\\x86\\x92 Email, then follow the prompts to connect your email provider (Gmail, Outlook, or custom", + "title": "Support queries related playbook" + }, + { + "id": "ART-2047_KNOWLEDGE_NODE-37", + "text": "**Settings** > **Integrations** > **AirSyncs**.\\n2. Locate the previously imported project.\\n3. Select **\\xe2\\x8b\\xae** > **Sync DevRev to Salesforce Service**.\\n\\n![]()\\n\\nThis may override fields in Salesforce of previously imported items, even if they were modified in Salesforce.\\n\\n#### Mark a DevRev ticket for syncing\\n\\nUsing the [Sync to Salesforce](#sync-to-salesforce) feature, it\\'s possible to sync DevRev tickets to Salesforce. In order to sync a DevRev ticket to a specific Salesforce", "title": "Salesforce AirSync | AirSync | Snap-ins | DevRev" }, { @@ -1918,13 +1923,13 @@ "title": "Salesforce AirSync | AirSync | Snap-ins | DevRev" }, { - "id": "ART-2047_KNOWLEDGE_NODE-30", - "text": "it\\'s your first).\\n2. Create a new connection to your Salesforce account, or use an existing connection if you already have one.\\n3. Once the connection is established, select the Salesforce account you want to import and specify the DevRev part that should be used for any imported cases without a product. This initiates a bulk import of the selected account.\\n4. DevRev makes an effort to automatically map the fields from Salesforce to corresponding fields in DevRev. However, you may be", + "id": "ART-2047_KNOWLEDGE_NODE-35", + "text": "longer available.\\n\\n### Sync to DevRev\\n\\nAfter a successful import from a Salesforce account, you can choose to sync the imported data with DevRev. This feature airdrops any new items and any changes made to previously imported items from Salesforce.\\n\\nTo perform a one-time sync to DevRev, follow these steps:\\n\\n1. Go to **Settings** > **Integrations** > **AirSyncs**.\\n2. Locate the previously imported project.\\n3. Select **\\xe2\\x8b\\xae** > **Sync Salesforce Service to", "title": "Salesforce AirSync | AirSync | Snap-ins | DevRev" }, { - "id": "ART-2047_KNOWLEDGE_NODE-32", - "text": "automatically.\\n\\nPost import options\\n-------------------\\n\\nAfter a successful import, you have the following options available for the imported account:\\n\\n* [Sync to DevRev](#sync-to-devrev):\\n + This option allows you to synchronize any modifications made in Salesforce with the corresponding items previously imported into DevRev. It also creates new items in DevRev for any new items created in Salesforce after the last sync or import. This is a one-time operation.\\n* [Sync to", + "id": "ART-2047_KNOWLEDGE_NODE-33", + "text": "Salesforce](#sync-to-salesforce):\\n + This option synchronizes any changes made in DevRev to previously synced Salesforce [supported items](#supported-objects) back to Salesforce. It also creates any [items marked in DevRev](#mark-a-devrev-ticket-for-syncing) for creation in Salesforce. This is a one-time operation.\\n* [Periodic Sync](#periodic-sync):\\n + By enabling this option, you can automatically sync new changes from Salesforce to DevRev on a periodic basis. The default frequency is", "title": "Salesforce AirSync | AirSync | Snap-ins | DevRev" }, { @@ -1933,29 +1938,24 @@ "title": "Salesforce AirSync | AirSync | Snap-ins | DevRev" }, { - "id": "ART-2047_KNOWLEDGE_NODE-33", - "text": "Salesforce](#sync-to-salesforce):\\n + This option synchronizes any changes made in DevRev to previously synced Salesforce [supported items](#supported-objects) back to Salesforce. It also creates any [items marked in DevRev](#mark-a-devrev-ticket-for-syncing) for creation in Salesforce. This is a one-time operation.\\n* [Periodic Sync](#periodic-sync):\\n + By enabling this option, you can automatically sync new changes from Salesforce to DevRev on a periodic basis. The default frequency is", + "id": "ART-2047_KNOWLEDGE_NODE-39", + "text": "created in the specified Salesforce account the next time the Sync from [DevRev to Salesforce](#sync-to-salesforce) runs. This can be triggered manually or automatically through a Periodic Sync. Future syncs keeps this item updated on both sides after it has been created in Salesforce.\\n\\n### Historical AirSyncs\\n\\nTo view currently running and previous AirSyncs from various sources, do the following:\\n\\n1. Go to **Settings** > **Integrations** > **AirSyncs**.\\n2. Select the import you want to", "title": "Salesforce AirSync | AirSync | Snap-ins | DevRev" }, { - "id": "ART-2047_KNOWLEDGE_NODE-37", - "text": "**Settings** > **Integrations** > **AirSyncs**.\\n2. Locate the previously imported project.\\n3. Select **\\xe2\\x8b\\xae** > **Sync DevRev to Salesforce Service**.\\n\\n![]()\\n\\nThis may override fields in Salesforce of previously imported items, even if they were modified in Salesforce.\\n\\n#### Mark a DevRev ticket for syncing\\n\\nUsing the [Sync to Salesforce](#sync-to-salesforce) feature, it\\'s possible to sync DevRev tickets to Salesforce. In order to sync a DevRev ticket to a specific Salesforce", - "title": "Salesforce AirSync | AirSync | Snap-ins | DevRev" + "id": "ART-13117_KNOWLEDGE_NODE-5", + "text": "don't care about updates from Zendesk. How should I set up everything in DevRev?\\n\\nYou should tell your customer support representative that you want to enable merging of accounts for Salesforce and Zendesk syncs, and that you would like to sync updates from Salesforce even after merging. After the Airdrop team has enabled the automatic merging you should do a full Salesforce import, so that all the accounts from Salesforce are imported into DevRev. Then you can do a Zendesk import into", + "title": "Airdrop duplicates merging" }, { - "id": "ART-2047_KNOWLEDGE_NODE-25", - "text": "AirSync](/docs/integrations/salesforce)\\n\\nSalesforce AirSync\\n==================\\n\\nDevRev\\'s Salesforce AirSync allows you to perform a bulk migration, ongoing 1-way sync, or ongoing 2-way syncs. A bulk import is a prerequisite to setting up a sync.\\n\\n![]()\\n\\nFor more information, refer to the [Salesforce AirSync snap-in](https://marketplace.devrev.ai/salesforce) on the DevRev marketplace.\\n\\nSupported objects\\n-----------------\\n\\nThe following is a list of Salesforce objects and their", + "id": "ART-2047_KNOWLEDGE_NODE-24", + "text": "options](#post-import-options)\\n* [Sync to DevRev](#sync-to-devrev)\\n* [Sync to Salesforce](#sync-to-salesforce)\\n* [Mark a DevRev ticket for syncing](#mark-a-devrev-ticket-for-syncing)\\n* [AirSync Salesforce scope and limitations](#airsync-salesforce-scope-and-limitations)\\n* [Comments](#comments)\\n* [Updates](#updates)\\n* [Knowledge articles](#knowledge-articles)\\n\\n1. [Documentation](/docs)\\n3. [Snap-ins](/docs/snapins)\\n[AirSync](/docs/import)\\n[Salesforce", "title": "Salesforce AirSync | AirSync | Snap-ins | DevRev" }, { - "id": "ART-2045_KNOWLEDGE_NODE-49", - "text": "associated with the account you want to merge from will be associated with the account to be merged with.\\n4. Click **Merge**.\\n\\nContact deduplication\\n---------------------\\n\\nDevRev contacts help you keep track of your [customers](https://docs.devrev.ai/product/customers). Contacts are the individual users, which may or may not be associated with an account. DevRev contacts aren\\'t globally unique. The same user may have multiple contact records.\\n\\nAirSync imported contacts are deduplicated", - "title": "AirSync | Snap-ins | DevRev" - }, - { - "id": "ART-2045_KNOWLEDGE_NODE-46", - "text": "organizations in Zendesk, or accounts in Salesforce.\\n\\nAn AirSync doesn\\'t deduplicate imported accounts; rather, it modifies them so that new accounts don\\'t violate DevRev constraints. These accounts can be merged after the import has been completed. Since DevRev has several constraints on the uniqueness of different DevRev account fields, AirSync avoids breaking these constraints by following these rules when another account is already using the unique value:\\n\\n| Account Field | Rule |\\n|", - "title": "AirSync | Snap-ins | DevRev" + "id": "ART-2047_KNOWLEDGE_NODE-30", + "text": "it\\'s your first).\\n2. Create a new connection to your Salesforce account, or use an existing connection if you already have one.\\n3. Once the connection is established, select the Salesforce account you want to import and specify the DevRev part that should be used for any imported cases without a product. This initiates a bulk import of the selected account.\\n4. DevRev makes an effort to automatically map the fields from Salesforce to corresponding fields in DevRev. However, you may be", + "title": "Salesforce AirSync | AirSync | Snap-ins | DevRev" } ] }, @@ -1964,54 +1964,54 @@ "query": "best way to export accounts in bulk", "retrievals": [ { - "id": "ART-1254_KNOWLEDGE_NODE-9", - "text": "Export Accounts (POST)\\n\\nNext](/api-reference/accounts/export-post)[Built with](https://buildwithfern.com/?utm_campaign=buildWith&utm_medium=docs&utm_source=developer.devrev.ai)'", - "title": "Export Accounts | DevRev | Docs" + "id": "ART-1303_KNOWLEDGE_NODE-6", + "text": "exported accounts.\\nShow 18 properties\\nGET / accounts.export\\n$ curl -G https://api.devrev.ai/accounts.export \\\\ > -H \" Authorization: Bearer \" \\\\ > --data-urlencode created_date.after=2023-01-01T12:00:00Z \\\\ > --data-urlencode created_date.before=2023-01-01T12:00:00Z \\\\ > --data-urlencode modified_date.after=2023-01-01T12:00:00Z \\\\ > --data-urlencode modified_date.before=2023-01-01T12:00:00Z\\n200 Retrieved 1 { 2 \" accounts \" : [ 3 { 4 \" created_date \" : \" 2023-01-01T12:00:00Z \" , 5 \"", + "title": "Export Post \u2014 DevRev | Docs" }, { - "id": "ART-1254_KNOWLEDGE_NODE-1", - "text": "it](/api-reference/accounts/export?explorer=true)\\n\\n200Retrieved\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | { |\\n| 2 | \"accounts\": [ |\\n| 3 | { |\\n| 4 | \"id\": \"string\", |\\n| 5 | \"owned_by\": [ |\\n| 6 | { |\\n| 7 | \"display_id\": \"string\", |\\n| 8 | \"id\": \"string\", |\\n| 9 | \"display_name\": \"string\", |\\n| 10 | \"display_picture\": { |\\n| 11 | \"display_id\": \"string\", |\\n| 12 | \"id\": \"string\", |\\n| 13 | \"file\": { |\\n| 14 | \"type\": \"string\", |\\n| 15 | \"name\": \"string\", |\\n| 16 | \"size\": 1 |\\n| 17 | } |\\n| 18", + "id": "ART-1254_KNOWLEDGE_NODE-0", + "text": "b'Export Accounts | DevRev | Docs\\n\\n[![]()![]()](https://developer.devrev.ai/)\\n\\nPublic\\n\\nPublic\\n\\nSearch\\n\\n`/`\\n\\n[API Reference](/api-reference/getting-started)[accounts](/api-reference/accounts/accounts)\\n\\nExport Accounts\\n===============\\n\\nCopy page\\n\\nGET\\n\\nhttps://api.devrev.ai/accounts.export\\n\\nGET\\n\\n/accounts.export\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl https://api.devrev.ai/accounts.export \\\\ |\\n| > | -H \"Authorization: Bearer \" |\\n```\\n\\n[Try", "title": "Export Accounts | DevRev | Docs" }, { - "id": "ART-1254_KNOWLEDGE_NODE-0", - "text": "b'Export Accounts | DevRev | Docs\\n\\n[![]()![]()](https://developer.devrev.ai/)\\n\\nPublic\\n\\nPublic\\n\\nSearch\\n\\n`/`\\n\\n[API Reference](/api-reference/getting-started)[accounts](/api-reference/accounts/accounts)\\n\\nExport Accounts\\n===============\\n\\nCopy page\\n\\nGET\\n\\nhttps://api.devrev.ai/accounts.export\\n\\nGET\\n\\n/accounts.export\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl https://api.devrev.ai/accounts.export \\\\ |\\n| > | -H \"Authorization: Bearer \" |\\n```\\n\\n[Try", - "title": "Export Accounts | DevRev | Docs" + "id": "ART-1255_KNOWLEDGE_NODE-0", + "text": "b'Export Accounts (POST) | DevRev | Docs\\n\\n[![]()![]()](https://developer.devrev.ai/)\\n\\nPublic\\n\\nPublic\\n\\nSearch\\n\\n`/`\\n\\n[API Reference](/api-reference/getting-started)[accounts](/api-reference/accounts/accounts)\\n\\nExport Accounts (POST)\\n======================\\n\\nCopy page\\n\\nPOST\\n\\nhttps://api.devrev.ai/accounts.export\\n\\nPOST\\n\\n/accounts.export\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl -X POST https://api.devrev.ai/accounts.export \\\\ |\\n| > | -H \"Authorization: Bearer \" \\\\", + "title": "Export Accounts (POST) | DevRev | Docs" }, { - "id": "ART-1449_KNOWLEDGE_NODE-1", - "text": "__\\n\\n[Pricing](https://devrev.ai/pricing)\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](https://devrev.ai/request-a-demo)\\n\\n[API Reference](/public/api-reference/getting-started)[Accounts](/public/api-reference/accounts/accounts)\\n\\n# Export Accounts\\n\\nGET\\n\\nhttps://api.devrev.ai/accounts.export\\n\\nTry it\\n\\nExports a collection of accounts.\\n\\n### Query parameters\\n\\ncreated_bylist of stringsOptional\\n\\nFilters for accounts created by the specified", - "title": "Export Accounts \u2014 DevRev | Docs" + "id": "ART-2000_KNOWLEDGE_NODE-24", + "text": "accounts](#bulk-import-accounts)\\n* [Using DevRev APIs](#using-devrev-apis)\\n* [Account attributes](#account-attributes)\\n* [External reference](#external-reference)\\n* [Add a workspace](#add-a-workspace)\\n\\n1. [Documentation](/docs)\\n3. [Computer for Growth Teams](/docs/product/grow)\\n[Accounts](/docs/product/account)\\n\\nAccount\\n=======\\n\\nAn account represents a customer organization, and it holds information about the company, including its name, address, industry, domain, and website", + "title": "Accounts | Computer for Growth Teams | DevRev" }, { - "id": "ART-1255_KNOWLEDGE_NODE-1", - "text": "|\\n| > | -H \"Content-Type: application/json\" \\\\ |\\n| > | -d \\'{}\\' |\\n```\\n\\n[Try it](/api-reference/accounts/export-post?explorer=true)\\n\\n200Successful\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | { |\\n| 2 | \"accounts\": [ |\\n| 3 | { |\\n| 4 | \"id\": \"string\", |\\n| 5 | \"owned_by\": [ |\\n| 6 | { |\\n| 7 | \"display_id\": \"string\", |\\n| 8 | \"id\": \"string\", |\\n| 9 | \"display_name\": \"string\", |\\n| 10 | \"display_picture\": { |\\n| 11 | \"display_id\": \"string\", |\\n| 12 | \"id\": \"string\", |\\n| 13 | \"file\": { |\\n| 14", - "title": "Export Accounts (POST) | DevRev | Docs" + "id": "ART-1305_KNOWLEDGE_NODE-6", + "text": "exported accounts.\\nShow 18 properties\\nAPI Reference accounts Export Post.\\n\\nPOST https:// api.devrev.ai / accounts.export\\nExports a collection of accounts.\\nRequest.\\n\\nThis endpoint expects an object.\\ncreated_by list of strings Optional\\nFilters for accounts created by the specified user(s).\\ncreated_date object Optional\\nShow 2 properties\\ncustom_fields map from strings to any Optional\\nFilters for custom fields.\\ndisplay_name list of strings Optional\\nArray of display names of accounts", + "title": "Get Post \u2014 DevRev | Docs" }, { - "id": "ART-1255_KNOWLEDGE_NODE-0", - "text": "b'Export Accounts (POST) | DevRev | Docs\\n\\n[![]()![]()](https://developer.devrev.ai/)\\n\\nPublic\\n\\nPublic\\n\\nSearch\\n\\n`/`\\n\\n[API Reference](/api-reference/getting-started)[accounts](/api-reference/accounts/accounts)\\n\\nExport Accounts (POST)\\n======================\\n\\nCopy page\\n\\nPOST\\n\\nhttps://api.devrev.ai/accounts.export\\n\\nPOST\\n\\n/accounts.export\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl -X POST https://api.devrev.ai/accounts.export \\\\ |\\n| > | -H \"Authorization: Bearer \" \\\\", - "title": "Export Accounts (POST) | DevRev | Docs" + "id": "ART-1650_KNOWLEDGE_NODE-6", + "text": "exported accounts.\\nShow 18 properties\\nAPI Reference accounts Export Post.\\n\\nPOST https:// api.devrev.ai / accounts.export\\nExports a collection of accounts.\\nRequest.\\n\\nThis endpoint expects an object.\\ncreated_by list of strings Optional\\nFilters for accounts created by the specified user(s).\\ncreated_date object Optional\\nShow 2 properties\\ncustom_fields map from strings to any Optional\\nFilters for custom fields.\\ndisplay_name list of strings Optional\\nArray of display names of accounts", + "title": "List Post \u2014 DevRev | Docs" }, { - "id": "ART-1449_KNOWLEDGE_NODE-10", - "text": "\"modified_date\": \"2023-01-01T12:00:00.000Z\", \\n 69| \"primary_account\": { \\n 70| \"id\": \"foo\", \\n 71| \"display_id\": \"foo\", \\n 72| \"display_name\": \"foo\" \\n 73| }, \\n 74| \"tier\": \"foo\", \\n 75| \"websites\": [ \\n 76| \"foo\" \\n 77| ] \\n 78| } \\n 79| ] \\n 80| }\\n[/code] \\n \\n[Export Accounts (POST)Up Next](/public/api-reference/accounts/export-post)\\n\\n[Built", - "title": "Export Accounts \u2014 DevRev | Docs" + "id": "ART-1824_KNOWLEDGE_NODE-6", + "text": "exported accounts.\\nShow 18 properties\\nAPI Reference accounts Export Post.\\n\\nPOST https:// api.devrev.ai / accounts.export\\nExports a collection of accounts.\\nRequest.\\n\\nThis endpoint expects an object.\\ncreated_by list of strings Optional\\nFilters for accounts created by the specified user(s).\\ncreated_date object Optional\\nShow 2 properties\\ncustom_fields map from strings to any Optional\\nFilters for custom fields.\\ndisplay_name list of strings Optional\\nArray of display names of accounts", + "title": "Delete \u2014 DevRev | Docs" }, { - "id": "ART-1462_KNOWLEDGE_NODE-0", - "text": "b'[](/public/api-reference/accounts/export-post)\\n\\nPublic\\n\\n[API Reference](/public/api-reference/getting-started)[Accounts](/public/api-reference/accounts/accounts)\\n\\n# Export Accounts (POST)\\n\\nPOST\\n\\nhttps://api.devrev.ai/accounts.export\\n\\nTry it\\n\\nExports a collection of accounts.\\n\\n### Request\\n\\nThis endpoint expects an object.\\n\\ncreated_bylist of stringsOptional\\n\\nFilters for accounts created by the specified user(s).\\n\\ncreated_dateobjectOptional\\n\\nShow 2", - "title": "Export Accounts (POST) \u2014 DevRev | Docs" + "id": "ART-1593_KNOWLEDGE_NODE-6", + "text": "exported accounts.\\nShow 18 properties\\nAPI Reference accounts Export Post.\\n\\nPOST https:// api.devrev.ai / accounts.export\\nExports a collection of accounts.\\nRequest.\\n\\nThis endpoint expects an object.\\ncreated_by list of strings Optional\\nFilters for accounts created by the specified user(s).\\ncreated_date object Optional\\nShow 2 properties\\ncustom_fields map from strings to any Optional\\nFilters for custom fields.\\ndisplay_name list of strings Optional\\nArray of display names of accounts", + "title": "Get \u2014 DevRev | Docs" }, { - "id": "ART-1449_KNOWLEDGE_NODE-0", - "text": "b'[](/public/api-reference/accounts/export)\\n\\nPublic\\n\\n[](https://devrev.ai)\\n\\n * Product\\n * Platform\\n * Solutions\\n * Marketplace\\n * Company\\n * Resources\\n * [Pricing](https://devrev.ai/pricing)\\n\\n __\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](https://devrev.ai/request-a-demo)\\n\\n[](https://devrev.ai)\\n\\n __\\n\\nProduct __\\n\\nPlatform __\\n\\nSolutions __\\n\\nMarketplace __\\n\\nCompany __\\n\\nResources", - "title": "Export Accounts \u2014 DevRev | Docs" + "id": "ART-1802_KNOWLEDGE_NODE-6", + "text": "exported accounts.\\nShow 18 properties\\nAPI Reference accounts Export Post.\\n\\nPOST https:// api.devrev.ai / accounts.export\\nExports a collection of accounts.\\nRequest.\\n\\nThis endpoint expects an object.\\ncreated_by list of strings Optional\\nFilters for accounts created by the specified user(s).\\ncreated_date object Optional\\nShow 2 properties\\ncustom_fields map from strings to any Optional\\nFilters for custom fields.\\ndisplay_name list of strings Optional\\nArray of display names of accounts", + "title": "Get Post \u2014 DevRev | Docs" }, { - "id": "ART-1449_KNOWLEDGE_NODE-5", - "text": "Unavailable Error\\n\\nGET\\n\\n/accounts.export\\n\\n[code]\\n\\n $| curl https://api.devrev.ai/accounts.export \\\\ \\n ---|--- \\n >| -H \"Authorization: Bearer \"\\n[/code] \\n \\nTry it\\n\\n200exportExample\\n\\n[code]\\n\\n 1| { \\n ---|--- \\n 2| \"accounts\": [ \\n 3| { \\n 4| \"id\": \"foo\", \\n 5| \"owned_by\": [ \\n 6| { \\n 7| \"display_id\": \"foo\", \\n 8| \"id\": \"foo\", \\n 9| \"display_name\": \"foo\", \\n", - "title": "Export Accounts \u2014 DevRev | Docs" + "id": "ART-1643_KNOWLEDGE_NODE-6", + "text": "exported accounts.\\nShow 18 properties\\nAPI Reference accounts Export Post.\\n\\nPOST https:// api.devrev.ai / accounts.export\\nExports a collection of accounts.\\nRequest.\\n\\nThis endpoint expects an object.\\ncreated_by list of strings Optional\\nFilters for accounts created by the specified user(s).\\ncreated_date object Optional\\nShow 2 properties\\ncustom_fields map from strings to any Optional\\nFilters for custom fields.\\ndisplay_name list of strings Optional\\nArray of display names of accounts", + "title": "List Post \u2014 DevRev | Docs" } ] }, @@ -2020,54 +2020,54 @@ "query": "copy schema subtype deal registration leaf type of account", "retrievals": [ { - "id": "ART-4116_KNOWLEDGE_NODE-0", - "text": "b'[](/beta/api-reference/customization/schemas-subtype-prepare-update-get)\\n\\nBeta\\n\\n[API Reference](/beta/api-reference/accounts/create)[Customization](/beta/api-reference/customization/custom-objects-count)\\n\\n# Prepare-Update Schemas Subtypes\\n\\nPOST\\n\\nhttps://api.devrev.ai/schemas.subtypes.prepare-update\\n\\nTry it\\n\\nGets the new fragment IDs and fields resulting from changing a subtype.\\n\\n### Request\\n\\nThis endpoint expects an object.\\n\\nleaf_typestringRequired`format: \"text\"`\\n\\nLeaf", - "title": "Prepare-Update Schemas Subtypes (Beta) \u2014 DevRev | Docs" + "id": "ART-15337_KNOWLEDGE_NODE-19", + "text": "subtype.\\n\\nis\\\\_custom\\\\_leaf\\\\_typebooleanOptional\\n\\nWhether the leaf type corresponds to a custom object.\\n\\nleaf\\\\_typestringOptional`format: \"text\"`\\n\\nThe leaf type. Used for inferring the default stage diagram and\\ntenant fragment ID.\\n\\nstock\\\\_schema\\\\_fragmentstringOptional`format: \"id\"`\\n\\nThe stock schema fragment which is to be aggregated.\\n\\n### Response\\n\\nSuccess.\\n\\nschemaobject\\n\\nList of custom fields from multiple source fragments.\\n\\nShow 13 properties\\n\\n###", + "title": "Get Schemas Aggregated | DevRev | Docs" }, { - "id": "ART-15342_KNOWLEDGE_NODE-3", - "text": "token.\\n\\n### Request\\n\\nThis endpoint expects an object.\\n\\nleaf\\\\_typestringRequired`format: \"text\"`\\n\\nLeaf type of the object.\\n\\nis\\\\_custom\\\\_leaf\\\\_typebooleanOptional\\n\\nWhether the leaf type corresponds to a custom object.\\n\\nnew\\\\_subtypestringOptional`format: \"text\"`\\n\\nName of the new subtype for the object.\\n\\nobjectstringOptional`format: \"id\"`\\n\\nID of the object of which subtype is to be changed. Used to fetch\\nthe object\\'s custom schema fragments and custom fields\\n\\n###", - "title": "Prepare-Update Schemas Subtypes | DevRev | Docs" + "id": "ART-1602_KNOWLEDGE_NODE-2", + "text": "DONs which are to be aggregated.\\n\\ncustom_schema_spec.appslist of stringsOptional\\n\\nList of apps.\\n\\ncustom_schema_spec.subtypestringOptional`format: \"text\"`\\n\\nName of the subtype.\\n\\nis_custom_leaf_typebooleanOptional\\n\\nWhether the leaf type corresponds to a custom object.\\n\\nleaf_typestringOptional`format: \"text\"`\\n\\nThe leaf type. Used for inferring the default stage diagram and tenant fragment ID.\\n\\nstock_schema_fragment_idstringOptional`format: \"id\"`\\n\\nThe stock schema fragment which", + "title": "Get Schemas Aggregated (Beta) \u2014 DevRev | Docs" }, { - "id": "ART-15337_KNOWLEDGE_NODE-19", - "text": "subtype.\\n\\nis\\\\_custom\\\\_leaf\\\\_typebooleanOptional\\n\\nWhether the leaf type corresponds to a custom object.\\n\\nleaf\\\\_typestringOptional`format: \"text\"`\\n\\nThe leaf type. Used for inferring the default stage diagram and\\ntenant fragment ID.\\n\\nstock\\\\_schema\\\\_fragmentstringOptional`format: \"id\"`\\n\\nThe stock schema fragment which is to be aggregated.\\n\\n### Response\\n\\nSuccess.\\n\\nschemaobject\\n\\nList of custom fields from multiple source fragments.\\n\\nShow 13 properties\\n\\n###", - "title": "Get Schemas Aggregated | DevRev | Docs" + "id": "ART-15502_KNOWLEDGE_NODE-3", + "text": "\\xe2\\x80\\x9ccampaign\\xe2\\x80\\x9d.\\n2. **Subtype**: A categorization of a leaf type. For example, \\xe2\\x80\\x9cpromotion\\xe2\\x80\\x9d or \\xe2\\x80\\x9cadvertising\\xe2\\x80\\x9d for a \\xe2\\x80\\x9ccampaign\\xe2\\x80\\x9d leaf type.\\n3. **Schema fragment**: A schema fragment defines the schema for an object.\\n4. **Custom fields**: User-defined fields that store specific data for your custom object.\\n5. **ID prefix**: A unique prefix used to generate the display ID for the custom object. If the `id_prefix`", + "title": "Custom objects | DevRev | Docs" }, { - "id": "ART-4116_KNOWLEDGE_NODE-1", - "text": "type of the object.\\n\\nis_custom_leaf_typebooleanOptional\\n\\nWhether the leaf type corresponds to a custom object.\\n\\nnew_subtypestringOptional`format: \"text\"`\\n\\nName of the new subtype for the object.\\n\\nobjectstringOptional`format: \"id\"`\\n\\nID of the object of which subtype is to be changed. Used to fetch the object\\xe2\\x80\\x99s custom schema fragments and custom fields\\n\\n### Response\\n\\nSuccess.\\n\\nadded_fieldslist of objectsOptional\\n\\nList of fields that have a default value and need to", - "title": "Prepare-Update Schemas Subtypes (Beta) \u2014 DevRev | Docs" + "id": "ART-2683_KNOWLEDGE_NODE-3", + "text": "**Subtype** : A categorization of a leaf type. For example, \\xe2\\x80\\x9cpromotion\\xe2\\x80\\x9d or \\xe2\\x80\\x9cadvertising\\xe2\\x80\\x9d for a \\xe2\\x80\\x9ccampaign\\xe2\\x80\\x9d leaf type.\\n 3. **Schema fragment** : A schema fragment defines the schema for an object.\\n 4. **Custom fields** : User-defined fields that store specific data for your custom object.\\n 5. **Unique key** : A unique identifier for each custom object. This is useful for maintaining idempotency when retrying custom object", + "title": "Custom objects (Beta) \u2014 DevRev | Docs" }, { - "id": "ART-16108_KNOWLEDGE_NODE-0", - "text": "b'Airdrop does not allow changing which subtype it syncs work items to. The subtypes that Airdrop creates, are maintained by Airdrop, because they have to reflect the schema they the customer has in the external system (custom fields, field values, stages etc. all have to exactly match the external system schema). To modify the subtype, one should modify the schema in the external system.'", - "title": "Airdrop Work Subtype Schema" + "id": "ART-1780_KNOWLEDGE_NODE-226", + "text": "leaf types for which subtypes are required.\\nResponse.\\n\\nThis endpoint returns an object.\\nsubtypes list of objects\\nList of subtypes.\\nShow 4 properties\\nAPI Reference customization Subtypes List Post.\\n\\nPOST https:// api.devrev.ai / schemas.subtypes.list\\nLists subtypes.\\nRequest.\\n\\nThis endpoint expects an object.\\nleaf_type string Optional\\nLeaf type for which subtypes are required.\\nleaf_types list of strings Optional\\nList of leaf types for which subtypes are", + "title": "Get Post \u2014 DevRev | Docs" }, { - "id": "ART-1614_KNOWLEDGE_NODE-4", - "text": "with](https://buildwithfern.com/?utm_campaign=buildWith&utm_medium=docs&utm_source=developer.devrev.ai)'", - "title": "List Schemas Subtypes (POST) | DevRev | Docs" + "id": "ART-1786_KNOWLEDGE_NODE-226", + "text": "leaf types for which subtypes are required.\\nResponse.\\n\\nThis endpoint returns an object.\\nsubtypes list of objects\\nList of subtypes.\\nShow 4 properties\\nAPI Reference customization Subtypes List Post.\\n\\nPOST https:// api.devrev.ai / schemas.subtypes.list\\nLists subtypes.\\nRequest.\\n\\nThis endpoint expects an object.\\nleaf_type string Optional\\nLeaf type for which subtypes are required.\\nleaf_types list of strings Optional\\nList of leaf types for which subtypes are", + "title": "Delete \u2014 DevRev | Docs" }, { - "id": "ART-1632_KNOWLEDGE_NODE-0", - "text": "b'List Schemas Subtypes | DevRev | Docs\\n\\n[![]()![]()](https://developer.devrev.ai/)\\n\\nBeta\\n\\nBeta\\n\\nBeta\\n\\nSearch\\n\\n`/`\\n\\n[API Reference](/beta/api-reference/accounts/create)[customization](/beta/api-reference/customization/custom-objects-count)\\n\\nList Schemas Subtypes\\n=====================\\n\\nBeta\\n\\nCopy page\\n\\nGET\\n\\nhttps://api.devrev.ai/schemas.subtypes.list\\n\\nGET\\n\\n/schemas.subtypes.list\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl https://api.devrev.ai/schemas.subtypes.list \\\\", - "title": "List Schemas Subtypes | DevRev | Docs" + "id": "ART-1308_KNOWLEDGE_NODE-228", + "text": "leaf types for which subtypes are required.\\nResponse.\\n\\nThis endpoint returns an object.\\nsubtypes list of objects\\nList of subtypes.\\nShow 4 properties\\nAPI Reference customization Subtypes List Post.\\n\\nPOST https:// api.devrev.ai / schemas.subtypes.list\\nLists subtypes.\\nRequest.\\n\\nThis endpoint expects an object.\\nleaf_type string Optional\\nLeaf type for which subtypes are required.\\nleaf_types list of strings Optional\\nList of leaf types for which subtypes are", + "title": "Update \u2014 DevRev | Docs" }, { - "id": "ART-15340_KNOWLEDGE_NODE-8", - "text": "\"id\": \"string\", |\\n| 124 | \"file\": { |\\n| 125 | \"type\": \"string\", |\\n| 126 | \"name\": \"string\", |\\n| 127 | \"size\": 1 |\\n| 128 | } |\\n| 129 | }, |\\n| 130 | \"email\": \"string\", |\\n| 131 | \"full_name\": \"string\", |\\n| 132 | \"state\": \"active\" |\\n| 133 | }, |\\n| 134 | \"created_date\": \"2023-01-01T12:00:00.000Z\", |\\n| 135 | \"description\": \"string\", |\\n| 136 | \"display_id\": \"string\", |\\n| 137 | \"leaf_type\": \"string\", |\\n| 138 | \"modified_by\": { |\\n| 139 | \"display_id\": \"string\", |\\n| 140 | \"id\": \"string\",", - "title": "List Schemas Stock | DevRev | Docs" + "id": "ART-1302_KNOWLEDGE_NODE-231", + "text": "leaf types for which subtypes are required.\\nResponse.\\n\\nThis endpoint returns an object.\\nsubtypes list of objects\\nList of subtypes.\\nShow 4 properties\\nAPI Reference customization Subtypes List Post.\\n\\nPOST https:// api.devrev.ai / schemas.subtypes.list\\nLists subtypes.\\nRequest.\\n\\nThis endpoint expects an object.\\nleaf_type string Optional\\nLeaf type for which subtypes are required.\\nleaf_types list of strings Optional\\nList of leaf types for which subtypes are", + "title": "Export \u2014 DevRev | Docs" }, { - "id": "ART-1560_KNOWLEDGE_NODE-153", - "text": "List Post.\\n\\nPOST https://api.devrev.ai / schemas.subtypes.list\\n\\nLists subtypes.\\n\\nRequest.\\n\\nThis endpoint expects an object.\\nleaf_type string Optional\\n\\nLeaf type for which subtypes are required.\\n\\nleaf_types list of strings Optional\\n\\nList of leaf types for which subtypes are required.\\n\\nResponse.\\n\\nThis endpoint returns an object.\\nsubtypes list of objects\\n\\nList of subtypes.\\n\\nShow 4 properties\\nAPI Reference customization Custom Stages Create.\\n\\nPOST https://api.devrev.ai /", - "title": "Assign (Beta) \u2014 DevRev | Docs" + "id": "ART-1301_KNOWLEDGE_NODE-231", + "text": "leaf types for which subtypes are required.\\nResponse.\\n\\nThis endpoint returns an object.\\nsubtypes list of objects\\nList of subtypes.\\nShow 4 properties\\nAPI Reference customization Subtypes List Post.\\n\\nPOST https:// api.devrev.ai / schemas.subtypes.list\\nLists subtypes.\\nRequest.\\n\\nThis endpoint expects an object.\\nleaf_type string Optional\\nLeaf type for which subtypes are required.\\nleaf_types list of strings Optional\\nList of leaf types for which subtypes are", + "title": "Delete \u2014 DevRev | Docs" }, { - "id": "ART-1632_KNOWLEDGE_NODE-2", - "text": "`, where token is your auth token.\\n\\n### Query parameters\\n\\nleaf\\\\_typestringOptional`format: \"text\"`Deprecated\\n\\nLeaf type for which subtypes are required.\\n\\nleaf\\\\_typeslist of stringsOptional\\n\\nList of leaf types for which subtypes are required.\\n\\n### Response\\n\\nSuccess.\\n\\nsubtypeslist of objects\\n\\nList of subtypes.\\n\\nShow 4 properties\\n\\n### Errors\\n\\n400\\n\\nBad Request Error\\n\\n401\\n\\nUnauthorized Error\\n\\n403\\n\\nForbidden Error\\n\\n429\\n\\nToo Many Requests", - "title": "List Schemas Subtypes | DevRev | Docs" + "id": "ART-1792_KNOWLEDGE_NODE-229", + "text": "leaf types for which subtypes are required.\\nResponse.\\n\\nThis endpoint returns an object.\\nsubtypes list of objects\\nList of subtypes.\\nShow 4 properties\\nAPI Reference customization Subtypes List Post.\\n\\nPOST https:// api.devrev.ai / schemas.subtypes.list\\nLists subtypes.\\nRequest.\\n\\nThis endpoint expects an object.\\nleaf_type string Optional\\nLeaf type for which subtypes are required.\\nleaf_types list of strings Optional\\nList of leaf types for which subtypes are", + "title": "Update \u2014 DevRev | Docs" } ] }, @@ -2076,54 +2076,54 @@ "query": "Automatic case classification by product, severity, and category", "retrievals": [ { - "id": "ART-17515_KNOWLEDGE_NODE-25", - "text": "summary: Provides a summary of initial customer emails on tickets.\\n* Spacebar summaries: Offers quick summaries of the **Updates** page, account records, and conversations.\\n* Ticket and issue clustering: Groups similar tickets and issues together for easier management.\\n* AI-generated enhancement descriptions: Creates detailed descriptions for enhancements based on the titles and descriptions of the enhancements and the linked objects.\\n* Request classification: Differentiates between bugs", - "title": "AI use cases in DevRev | Computer by DevRev | DevRev" + "id": "ART-4181_KNOWLEDGE_NODE-8", + "text": "metrics such as response time and resolution time, or tailor metrics to your requirements\\n\\n![]()\\n\\nTrigger SLAs at the right moment, every time\\n\\nMap conditions to parts of your product, tags, severity levels, or any other relevant criteria on our simple UI\\n\\n![]()\\n\\nTrigger SLAs at the right moment, every time\\n\\nMap conditions to parts of your product, tags, severity levels, or any other relevant criteria on our simple UI\\n\\n![]()\\n\\nSLAs in sync with your business\\n\\nAccount for", + "title": "Support like a lightning fast pit-crew" }, { - "id": "ART-17515_KNOWLEDGE_NODE-12", - "text": "sync](/docs/automations/org-tags-sync)\\n - [Search Node](/docs/automations/search-node)\\n - [Sentiment evaluator](/docs/automations/sentiment-evaluator)\\n - [Subtype Migration](/docs/automations/subtype-migration)\\n - [Real-time sentiment evaluator](/docs/automations/realtime-sentiment-evaluator)\\n - [Send customized emails](/docs/automations/send-emails)\\n - [StageFlow automator](/docs/automations/stageflow-automator)\\n - [Smart issue", - "title": "AI use cases in DevRev | Computer by DevRev | DevRev" + "id": "ART-4181_KNOWLEDGE_NODE-4", + "text": "tailor metrics to your requirements\\n\\n![]()\\n\\nTrigger SLAs at the right moment, every time\\n\\nMap conditions to parts of your product, tags, severity levels, or any other relevant criteria on our simple UI\\n\\n![]()\\n\\nTrigger SLAs at the right moment, every time\\n\\nMap conditions to parts of your product, tags, severity levels, or any other relevant criteria on our simple UI\\n\\n![]()\\n\\nSLAs in sync with your business\\n\\nAccount for calendar and business hours, ensuring that your SLAs", + "title": "Support like a lightning fast pit-crew" }, { - "id": "ART-17515_KNOWLEDGE_NODE-9", - "text": "[Automate](/docs/automate)\\n\\n - [Account deduplication](/docs/automations/account-deduplication)\\n - [Airtable](/docs/automations/airtable)\\n - [Auto-link DevRev GitHub accounts](/docs/automations/auto-link-github-devrev)\\n - [Automatic customer reply](/docs/automations/auto-reply)\\n - [Auto parts to conversation](/docs/automations/auto-parts)\\n - [Automated part update](/docs/automations/automated-part-update)\\n - [Automate opportunities](/docs/automations/opportunity)\\n", - "title": "AI use cases in DevRev | Computer by DevRev | DevRev" + "id": "ART-4181_KNOWLEDGE_NODE-2", + "text": "blog](/blog/sla)\\n\\nTrigger SLAs at the right moment, every time\\n\\nMap conditions to parts of your product, tags, severity levels, or any other relevant criteria on our simple UI\\n\\n![]()\\n\\nTrigger SLAs at the right moment, every time\\n\\nMap conditions to parts of your product, tags, severity levels, or any other relevant criteria on our simple UI\\n\\n![]()\\n\\nSLAs in sync with your business\\n\\nAccount for calendar and business hours, ensuring that your SLAs accurately reflect your support", + "title": "Support like a lightning fast pit-crew" }, { - "id": "ART-17515_KNOWLEDGE_NODE-1", - "text": "[Groups](/docs/product/groups)\\n + [Parts & trails](/docs/product/parts)\\n + [Vistas](/docs/product/vistas)\\n\\n - [Vista Reports](/docs/product/vista-reports)\\n - [Board view](/docs/product/board-view)\\n + [Tasks](/docs/product/tasks)\\n + [Updates](/docs/product/updates)\\n + [Customer email notifications](/docs/product/customer-emails)\\n + [Roles](/docs/product/roles)\\n\\n - [Default privileges by group](/docs/product/privs)\\n + [Access control](/docs/product/access-control)\\n +", - "title": "AI use cases in DevRev | Computer by DevRev | DevRev" + "id": "ART-4181_KNOWLEDGE_NODE-6", + "text": "time and resolution time, or tailor metrics to your requirements\\n\\n![]()\\n\\nTrigger SLAs at the right moment, every time\\n\\nMap conditions to parts of your product, tags, severity levels, or any other relevant criteria on our simple UI\\n\\n![]()\\n\\nTrigger SLAs at the right moment, every time\\n\\nMap conditions to parts of your product, tags, severity levels, or any other relevant criteria on our simple UI\\n\\n![]()\\n\\nSLAs in sync with your business\\n\\nAccount for calendar and business hours,", + "title": "Support like a lightning fast pit-crew" }, { - "id": "ART-17515_KNOWLEDGE_NODE-26", - "text": "and feature requests on tickets.\\n* Computer on Plug: Enhances the following functionalities:\\n\\n + Conversation: It deflects customer queries using your knowledge base, providing accurate and relevant responses.\\n + Search: It summarizes your search results, making information retrieval more efficient and user-friendly.\\n* Computer assist: Recommends relevant articles and similar work items.\\n* Slack tickets: Automatically generates titles and descriptions for tickets created from Slack", - "title": "AI use cases in DevRev | Computer by DevRev | DevRev" + "id": "ART-4129_KNOWLEDGE_NODE-21", + "text": "related docs.\\n\\nreported\\\\_bylist of longsOptional\\n\\nFilters for incidents with any of the provided reporters.\\n\\nseveritylist of longsOptional\\n\\nFilters for incidents containing any of the provided severities.\\n\\nsort\\\\_bylist of stringsOptional\\n\\nComma-separated fields to sort the incidents by.\\n\\nstagelist of stringsOptional\\n\\nFilters for incidents in any of the provided stages.\\n\\nstaged\\\\_infoobjectOptional\\n\\nShow 1 properties\\n\\nsubtypelist of stringsOptional\\n\\nFilters for", + "title": "Group Incidents (POST) | DevRev | Docs" }, { - "id": "ART-17515_KNOWLEDGE_NODE-4", - "text": "analytics](/docs/product/support-analytics)\\n\\n - [Conversation insights](/docs/dashboards/conversation-insights)\\n - [Conversation-SLA Analytics](/docs/dashboards/conversation-sla-analytics)\\n - [Conversation-Team Performance](/docs/dashboards/conversation-team-performance)\\n - [Ticket insights](/docs/dashboards/ticket-insights)\\n - [Ticket-SLA Analytics](/docs/dashboards/ticket-sla-analytics)\\n - [Ticket-Team Performance](/docs/dashboards/ticket-team-performance)\\n +", - "title": "AI use cases in DevRev | Computer by DevRev | DevRev" + "id": "ART-1641_KNOWLEDGE_NODE-177", + "text": "longs Optional\\nFilters for incidents containing any of the provided severities.\\nsort_by list of strings Optional\\nComma-separated fields to sort the incidents by.\\nsource list of longs Optional\\nFilters for incidents with any of the provided sources.\\nstage list of strings Optional\\nFilters for incidents in any of the provided stages.\\ntarget_close_date object Optional\\nProvides ways to specify date ranges on objects.\\nShow 2 variants\\ntitle list of strings Optional\\nFilters for incidents by", + "title": "Get Post \u2014 DevRev | Docs" }, { - "id": "ART-17515_KNOWLEDGE_NODE-10", - "text": "- [Bulk delete data](/docs/automations/bulk-delete)\\n - [Bulk work item uploader](/docs/automations/bulk-upload)\\n - [Commands surface expander](/docs/automations/commands-surface-expander)\\n - [Convergence](/docs/automations/converge)\\n - [Conversation reminder](/docs/automations/conversation-reminder)\\n - [CSAT on conversation](/docs/automations/csat-conv)\\n - [CSAT on ticket](/docs/automations/csat-tickets)\\n - [CSV work item", - "title": "AI use cases in DevRev | Computer by DevRev | DevRev" + "id": "ART-1597_KNOWLEDGE_NODE-177", + "text": "longs Optional\\nFilters for incidents containing any of the provided severities.\\nsort_by list of strings Optional\\nComma-separated fields to sort the incidents by.\\nsource list of longs Optional\\nFilters for incidents with any of the provided sources.\\nstage list of strings Optional\\nFilters for incidents in any of the provided stages.\\ntarget_close_date object Optional\\nProvides ways to specify date ranges on objects.\\nShow 2 variants\\ntitle list of strings Optional\\nFilters for incidents by", + "title": "Update \u2014 DevRev | Docs" }, { - "id": "ART-17515_KNOWLEDGE_NODE-13", - "text": "creator](/docs/automations/smart-issue-creator)\\n - [Set user preference for group](/docs/automations/set-user-preference)\\n - [SLA status change Slack notifier](/docs/automations/sla-change-notifier)\\n - [Slash commands](/docs/automations/slash-commands)\\n - [Spam Shield](/docs/automations/spam-shield)\\n - [Subtype Migration](/docs/automations/subtype-migration)\\n - [Ticket age in engineering](/docs/automations/ticket-age-in-engineering)\\n - [Ticket issue field", - "title": "AI use cases in DevRev | Computer by DevRev | DevRev" + "id": "ART-1577_KNOWLEDGE_NODE-177", + "text": "longs Optional\\nFilters for incidents containing any of the provided severities.\\nsort_by list of strings Optional\\nComma-separated fields to sort the incidents by.\\nsource list of longs Optional\\nFilters for incidents with any of the provided sources.\\nstage list of strings Optional\\nFilters for incidents in any of the provided stages.\\ntarget_close_date object Optional\\nProvides ways to specify date ranges on objects.\\nShow 2 variants\\ntitle list of strings Optional\\nFilters for incidents by", + "title": "Get Post \u2014 DevRev | Docs" }, { - "id": "ART-17515_KNOWLEDGE_NODE-15", - "text": "[Operational SLA Metrics](/docs/automations/operational-sla-metrics)\\n - [Custom field migration](/docs/automations/custom-field-migration)\\n - [Slack scraper](/docs/automations/slack-scraper)\\n - [Slack Broadcaster](/docs/automations/slack-broadcaster)\\n - [Reported by enricher](/docs/automations/ticket-reported-by)\\n - [Ticket approval workflow](/docs/automations/ticket-approval-workflow)\\n - [Ticket linked issues comment", - "title": "AI use cases in DevRev | Computer by DevRev | DevRev" + "id": "ART-1575_KNOWLEDGE_NODE-177", + "text": "longs Optional\\nFilters for incidents containing any of the provided severities.\\nsort_by list of strings Optional\\nComma-separated fields to sort the incidents by.\\nsource list of longs Optional\\nFilters for incidents with any of the provided sources.\\nstage list of strings Optional\\nFilters for incidents in any of the provided stages.\\ntarget_close_date object Optional\\nProvides ways to specify date ranges on objects.\\nShow 2 variants\\ntitle list of strings Optional\\nFilters for incidents by", + "title": "Delete \u2014 DevRev | Docs" }, { - "id": "ART-17515_KNOWLEDGE_NODE-24", - "text": "[Product demos](/docs/DevRevU/demos)\\n\\n1. [Documentation](/docs)\\n3. [Computer by DevRev](/docs/intro)\\n[AI use cases in DevRev](/docs/product/ai-use-cases)\\n\\nAI use cases in DevRev\\n======================\\n\\nAs an AI-native platform, Computer by DevRev leverages AI to provide value to customer support and product development staff. The following are some of the uses of AI in Computer.\\n\\n* Summary slash command: Generates summaries for internal and external discussions.\\n* Customer email", - "title": "AI use cases in DevRev | Computer by DevRev | DevRev" + "id": "ART-1509_KNOWLEDGE_NODE-179", + "text": "longs Optional\\nFilters for incidents containing any of the provided severities.\\nsort_by list of strings Optional\\nComma-separated fields to sort the incidents by.\\nsource list of longs Optional\\nFilters for incidents with any of the provided sources.\\nstage list of strings Optional\\nFilters for incidents in any of the provided stages.\\ntarget_close_date object Optional\\nProvides ways to specify date ranges on objects.\\nShow 2 variants\\ntitle list of strings Optional\\nFilters for incidents by", + "title": "Prepare \u2014 DevRev | Docs" } ] }, @@ -2132,54 +2132,54 @@ "query": "enable Generative AI for Knowledge Base creation", "retrievals": [ { - "id": "ART-13178_KNOWLEDGE_NODE-9", - "text": "articles, designs graphics, and generates code. It focuses on content creation based on prompts. According to [IBM research](https://www.ibm.com/think/topics/generative-ai-use-cases), 65% of enterprises now use generative AI for creation tasks like these.\\n\\nAgentic AI operates differently. It doesn\\xe2\\x80\\x99t just create \\xe2\\x80\\x93 it decides and acts. When your customer reports an issue, generative AI might draft a response to customer service inquiries, while agentic AI will investigate", - "title": "Understanding Agentic AI: Capabilities and Implications for the Future" + "id": "ART-1980_KNOWLEDGE_NODE-25", + "text": "knowledge base helps customers independently solve issues and assists employees in determining solutions to customer queries they\\xe2\\x80\\x99re resolving.\\n\\nThe articles can be created from scratch in DevRev, or they can be hosted on your own domain. Additionally, you can scrape articles from a previous database and import them into DevRev with the assistance of our support engineers.\\n\\nThere are multiple benefits to a knowledge base that can be accessed directly and through AI:\\n\\n*", + "title": "Knowledge Base | Computer for Support Teams | DevRev" }, { - "id": "ART-13178_KNOWLEDGE_NODE-12", - "text": "prompts | Predetermined logic paths only \\nImplementation examples | Self-directing customer journey managers, workflow orchestrators | Marketing copy generators, design assistants | Scheduled report generators, form processors \\nSystem connections | Operates across enterprise architecture | Generally functions as specialized tools | Isolated within specific applications \\nStrategic advantage | Full transformation of knowledge work processes | Enhanced productivity for content creation |", + "id": "ART-13178_KNOWLEDGE_NODE-9", + "text": "articles, designs graphics, and generates code. It focuses on content creation based on prompts. According to [IBM research](https://www.ibm.com/think/topics/generative-ai-use-cases), 65% of enterprises now use generative AI for creation tasks like these.\\n\\nAgentic AI operates differently. It doesn\\xe2\\x80\\x99t just create \\xe2\\x80\\x93 it decides and acts. When your customer reports an issue, generative AI might draft a response to customer service inquiries, while agentic AI will investigate", "title": "Understanding Agentic AI: Capabilities and Implications for the Future" }, { - "id": "ART-738_KNOWLEDGE_NODE-2", - "text": "they have. For example, both Chat GPT 3.5 and 4.0 were trained on the publicly available internet data as of September 2021, but they lack context about the current state. AutoGPT and others will help with this giving it the ability \\xe2\\x80\\x9cfetch\\xe2\\x80\\x9d additional context it may be lacking, however\\xe2\\x80\\xa6\\n\\n\\n That\\xe2\\x80\\x99s not the key, the key is in the data that you have that the models don\\xe2\\x80\\x99t have access to.\\n\\n\\n\\n\\nDevRev: built atop a badass knowledge", - "title": "DevRev | Built for AI (not by AI... yet)" + "id": "ART-4170_KNOWLEDGE_NODE-9", + "text": "Baldwa](/blog/explore-article-creation-and-analytics-dashboard)[![]()\\n\\n7 min read10 step guide to preparing your knowledge base for Gen AI search\\n\\nRhea Jain](/blog/guide-to-preparing-your-knowledge-base-for-ai-search)\\n\\n[![]()](/the-essential-methodology-whitepaper)\\n\\n[Dheeraj Pandey12 min read\\n\\n### Essential Methodology\\n\\n### Whitepaper for free\\n\\n\\xe2\\x9e\\xa4 The latest thinking on AI agents and platform](/the-essential-methodology-whitepaper)\\n\\n[Download", + "title": "DevRev | Blog" }, { - "id": "ART-13178_KNOWLEDGE_NODE-8", - "text": "intelligence system can track customer responses to support solutions, identify which approaches resolve issues fastest, and refine its methods accordingly.\\n\\n## Agentic AI vs generative AI\\n\\nGenerative AI creates content while agentic AI performs actions. This fundamental difference determines how each technology delivers business value through their distinct capabilities, applications, and limitations.\\n\\nYou\\xe2\\x80\\x99ve witnessed generative AI\\xe2\\x80\\x99s creative abilities. It writes", - "title": "Understanding Agentic AI: Capabilities and Implications for the Future" + "id": "ART-15792_KNOWLEDGE_NODE-9", + "text": "information sharing and reporting by converging support, product and user data in one shared view.\\n\\nAutomated knowledge base management: AI agents remember successful resolutions and instantly apply them to future issues, reducing customer wait time.\\n\\nSource: [DevRev Support](https://devrev.ai/support)BuildWhat is DevRev Build?\\n\\nDevRev Build is a full-featured product development platform built for modern businesses and trusted by leading organizations\\n\\nKey Features:\\n\\nAuto-generate", + "title": "DevRev Products and Agents" }, { - "id": "ART-970_KNOWLEDGE_NODE-67", - "text": "context, yet\\xe2\\x80\\xa6\\n\\n\\n That\\xe2\\x80\\x99s not the key, the key is in the data that you have that the models don\\xe2\\x80\\x99t have access to.\\n\\n\\nThe greater the context you can furnish through embeddings or fine-tuning, the more powerful AI becomes in your hands.\\n\\nThe Significance of Knowledge Graphs \\n\\nKnowledge graphs stand as invaluable tools that facilitate the organization and association of items based on various dimensions. Their utility extends beyond merely establishing", - "title": "The Story" + "id": "ART-1985_KNOWLEDGE_NODE-44", + "text": "Base**](https://app.devrev.ai/?setting=knowledge-base%2Farticles)** and select **View Templates**.\\n2. Select a template and click **Use Template**.\\n\\n### Edit a template\\n\\n1. Go to [**Settings** > **Customization** > **Templates**](https://app.devrev.ai/?setting=record-template).\\n2. Locate the template and click the **3-dot menu** under the **Action** column.\\n3. Click **Edit**, make your changes, and click **Publish**.\\n\\nContent blocks\\n--------------\\n\\nContent blocks let you create", + "title": "Articles | Knowledge Base | Computer for Support Teams | DevRev" }, { - "id": "ART-974_KNOWLEDGE_NODE-17", - "text": "tasks. For instance, AI-powered models can access and process vast amounts of information from the internet to answer queries, potentially rendering traditional search methods obsolete.\\n\\nFurthermore, AI\\xe2\\x80\\x99s influence extends to content creation, with AI-generated content becoming increasingly prevalent. This shift has the potential to alter the value of content, especially as AI could replace traditional search engines that index generated content. Businesses may need to adapt their", - "title": "Part I: Genesis" + "id": "ART-1771_KNOWLEDGE_NODE-6", + "text": "knowledge base integration.\\n\\nThe implementation validated DevRev\\'s capabilities and demonstrated remarkable speed. As Ankur noted: \"When I started using DevRev, the AirSync feature took me two hours to replace our previous solution, including transferring all knowledge articles.\" DevRev\\'s comprehensive documentation was particularly helpful during setup, allowing for a smooth transition without requiring extensive technical expertise.\\n\\nThe AI agent handles a large volume of routine", + "title": "ToughTrucksForKids.com achieves dramatic efficiency gains and customer satisfaction through AI-powered support automation" }, { - "id": "ART-13178_KNOWLEDGE_NODE-13", - "text": "Cost efficiency for repetitive activities \\n \\nGenerative AI excels at content-focused tasks. Agentic AI transforms process-oriented workflows.\\n\\n## What is the core framework of agentic AI?\\n\\nThe agentic AI framework consists of five interconnected components: perception, reasoning, action, learning, and collaboration. This structure enables autonomous agents to process information, make decisions, implement solutions, improve over time, and work alongside humans and other systems.\\n\\nYou", - "title": "Understanding Agentic AI: Capabilities and Implications for the Future" + "id": "ART-1039_KNOWLEDGE_NODE-11", + "text": "Knowledge base deflection\\n\\nMetrics and insightsThe Benefits\\n--------------------------------\\n\\n* Support is a competitive differentiation\\n* Scale to 100s of customers with fewer than 5 support engineers\\n* High-touch and personalized support\\n* Accelerated path to paid support tier\\n* AI-enhanced productivity and less context switching\\n\\n### Related Articles\\n\\n[![]()\\n\\n5 min readLuxCreo boosts operational efficiency and agility with DevRev](/case-study/luxcreo)[![]()\\n\\n5 min readAditya", + "title": "100ms delivers differentiated customer support through a unified channel" }, { - "id": "ART-974_KNOWLEDGE_NODE-2", - "text": "ourselves in the genesis of the AI revolution, a technological marvel that has reshaped our world. Large language models and generative transformers have ushered in a paradigm shift in our interactions with technology and information, challenging conventional search methods and unlocking new realms of creative potential.\\n\\nEvolution\\n\\n\\n\\n\\n \\xe2\\x80\\x9cIt is not the strongest of the species that survive, nor the most intelligent, but the one most responsive to change.\\xe2\\x80\\x9d - Charles", - "title": "Part I: Genesis" + "id": "ART-1985_KNOWLEDGE_NODE-32", + "text": "Base**](https://app.devrev.ai/?setting=knowledge-base%2Farticles) and select the article you want to edit. The article opens in an additional window on top of the knowledge base view.\\n Select the full screen mode icon to expand the article view.\\n2. Click the pen icon in the top right corner of the article to make the article editable.\\n3. Make the necessary changes and click **Save** or **Publish**.\\n\\n * If you **Save** the article, the changes are saved as a new draft version. Edits are", + "title": "Articles | Knowledge Base | Computer for Support Teams | DevRev" }, { - "id": "ART-13178_KNOWLEDGE_NODE-21", - "text": "**Prompt:** This defines the system\\xe2\\x80\\x99s operation blueprint, outlining specific goals and constraints. Think of it as the master plan guiding each agent. For complex systems, responsibilities are distributed across multiple AI agents to maintain simplicity and effectiveness.\\n * **Knowledge:** This serves as the agent\\xe2\\x80\\x99s knowledge repository, storing experiences and context. Like humans rely on past experiences, LLM agents use memory to understand situations and make", - "title": "Understanding Agentic AI: Capabilities and Implications for the Future" + "id": "ART-4168_KNOWLEDGE_NODE-7", + "text": "do it all: give AI models easy access to formerly siloed data and enable SQL query capabilities that power robust reporting and analytics - without performance trade-offs.\\n\\n![]()\\n\\n![]()\\n\\n![]()\\n\\nLATEST\\n\\nRead our white paper \\xe2\\x80\\x94 The conversational computer: toward human agency\\n\\n[READ THE WHITE PAPER](/blog/the-conversational-computer)\\n\\nLATEST\\n\\n![]()\\n\\nRead our white paper \\xe2\\x80\\x94 The conversational computer: toward human agency\\n\\n[READ THE WHITE", + "title": "Computer by DevRev: AI Infrastructure for Connected Enterprise Data | DevRev" }, { - "id": "ART-974_KNOWLEDGE_NODE-18", - "text": "content strategies to influence AI models and shape the information presented to users.\\n\\nLastly, AI has also impacted creativity, offering tools that change the way people envision, design, and iterate. These innovations empower individuals to create complex and detailed content independently. In fact, Midjourney was used to generate a great deal of the abstract images used throughout this book.\\n\\nWe have transitioned from a phase where AI was associated with apocalyptic scenarios to an era", - "title": "Part I: Genesis" + "id": "ART-4162_KNOWLEDGE_NODE-7", + "text": "do it all: give AI models easy access to formerly siloed data and enable SQL query capabilities that power robust reporting and analytics - without performance trade-offs.\\n\\n![]()\\n\\n![]()\\n\\n![]()\\n\\nLATEST\\n\\nRead our white paper \\xe2\\x80\\x94 The conversational computer: toward human agency\\n\\n[READ THE WHITE PAPER](/blog/the-conversational-computer)\\n\\nLATEST\\n\\n![]()\\n\\nRead our white paper \\xe2\\x80\\x94 The conversational computer: toward human agency\\n\\n[READ THE WHITE", + "title": "Computer by DevRev: AI Infrastructure for Connected Enterprise Data | DevRev" } ] }, @@ -2188,54 +2188,54 @@ "query": "Resource Center downloads tutorials API documentation", "retrievals": [ { - "id": "ART-1353_KNOWLEDGE_NODE-2", - "text": "[tutorial](/api-reference/getting-started) shows you how to access the APIs.\\n\\n\\xf0\\x9f\\xa7\\xac Methods\\n---------\\n\\nSpecifications covering the supported APIs are based on OpenAPI Specification 3.0. You can download the specs to use an OpenAPI 3.0-compliant tool to perform a variety of actions, including rendering them in UI and generating SDKs. Two [versions](/about/versioning) of the DevRev API are available: [public](/public) and [beta](/beta) (early access). Use the drop-down menu in the", - "title": "For Developers | DevRev | Docs" + "id": "ART-1617_KNOWLEDGE_NODE-5", + "text": "Next](/beta/api-reference/snap-ins/resources)\\n\\n[Built with](https://buildwithfern.com/?utm_campaign=buildWith&utm_medium=docs&utm_source=developer.devrev.ai)\\n\\n'", + "title": "Get Service Account (POST) (Beta) \u2014 DevRev | Docs" }, { - "id": "ART-3892_KNOWLEDGE_NODE-4", - "text": "* [Blog](https://devrev.ai/blog)\\n * [Events](https://devrev.ai/events)\\n * [News](https://devrev.ai/blog?category=news)\\n * [Case Studies](https://devrev.ai/case-study)\\n * [Documentation](https://docs.devrev.ai/)\\n * [API Reference](https://docs.devrev.ai/api/)\\n * [The Book of DevRev](https://thebook.devrev.ai/)\\n * [Partner Program](https://devrev.ai/partners)\\n * [Startup Program](https://devrev.ai/startups)\\n\\nCompany\\n\\n * [About](https://devrev.ai/about)\\n *", - "title": "API Changelog \u2014 DevRev | Docs" + "id": "ART-1364_KNOWLEDGE_NODE-5", + "text": "requested resource doesn\\xe2\\x80\\x99t exist. \\n`409`| `Conflict`| The attempted object creation conflicted with an existing object, for example, a group with the same name already exists. \\n \\nWas this page helpful?YesNo\\n\\n[Getting startedUp Next](/public/api-reference/getting-started)\\n\\n[Built with](https://buildwithfern.com/?utm_campaign=buildWith&utm_medium=docs&utm_source=developer.devrev.ai)\\n\\n[Enterprise grade security to protect customer dataLearn more about", + "title": "Errors \u2014 DevRev | Docs" }, { - "id": "ART-3194_KNOWLEDGE_NODE-6", - "text": "[Documentation](https://docs.devrev.ai/)\\n * [API Reference](https://docs.devrev.ai/api/)\\n * [The Book of DevRev](https://thebook.devrev.ai/)\\n * [Partner Program](https://devrev.ai/partners)\\n * [Startup Program](https://devrev.ai/startups)\\n\\nCompany\\n\\n * [About](https://devrev.ai/about)\\n * [People](https://devrev.ai/people)\\n * [Careers](https://devrev.ai/careers)\\n * [Places](https://devrev.ai/places)\\n * [Invest](https://revd.devrev.ai/)\\n * [What Why", - "title": "API Changelog \u2014 DevRev | Docs" + "id": "ART-1246_KNOWLEDGE_NODE-0", + "text": "b'Get Work | DevRev | Docs\\n\\n[![]()![]()](https://developer.devrev.ai/)\\n\\nPublic\\n\\nPublic\\n\\nSearch\\n\\n`/`\\n\\n[API Reference](/api-reference/getting-started)[works](/api-reference/works/tickets-and-issues)\\n\\nGet Work\\n========\\n\\nCopy page\\n\\nGET\\n\\nhttps://api.devrev.ai/works.get\\n\\nGET\\n\\n/works.get\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl -G https://api.devrev.ai/works.get \\\\ |\\n| > | -H \"Authorization: Bearer \" \\\\ |\\n| > | -d id=ISS-12345 |\\n```\\n\\n[Try", + "title": "Get Work | DevRev | Docs" }, { - "id": "ART-3193_KNOWLEDGE_NODE-6", - "text": "[Documentation](https://docs.devrev.ai/)\\n * [API Reference](https://docs.devrev.ai/api/)\\n * [The Book of DevRev](https://thebook.devrev.ai/)\\n * [Partner Program](https://devrev.ai/partners)\\n * [Startup Program](https://devrev.ai/startups)\\n\\nCompany\\n\\n * [About](https://devrev.ai/about)\\n * [People](https://devrev.ai/people)\\n * [Careers](https://devrev.ai/careers)\\n * [Places](https://devrev.ai/places)\\n * [Invest](https://revd.devrev.ai/)\\n * [What Why", - "title": "API Changes \u2014 DevRev | Docs" + "id": "ART-1175_KNOWLEDGE_NODE-0", + "text": "b'Getting started | DevRev | Docs\\n\\n[![]()![]()](https://developer.devrev.ai/)\\n\\nPublic\\n\\nPublic\\n\\nSearch\\n\\n`/`\\n\\nOn this page\\n\\n* [Prerequisites](/api-reference/getting-started#prerequisites)\\n* [Send your first API request](/api-reference/getting-started#send-your-first-api-request)\\n* [Making a GET request](/api-reference/getting-started#making-a-get-request)\\n* [Next steps](/api-reference/getting-started#next-steps)\\n\\n[API Reference](/api-reference/getting-started)\\n\\nGetting", + "title": "Getting started | DevRev | Docs" }, { - "id": "ART-1366_KNOWLEDGE_NODE-3", - "text": "covering the supported APIs are based on OpenAPI Specification 3.0. You can download the specs to use an OpenAPI 3.0-compliant tool to perform a variety of actions, including rendering them in UI and generating SDKs. Two [versions](/public/about/versioning) of the DevRev API are available: [public](/public) and [beta](/beta) (early access). Use the drop-down menu in the upper-left corner of this site to switch between versions.\\n\\nTo take action based on events from the DevRev platform,", - "title": "For Developers \u2014 DevRev | Docs" + "id": "ART-1619_KNOWLEDGE_NODE-1", + "text": "|\\n| > | -H \"Authorization: Bearer \" \\\\ |\\n| > | -H \"Content-Type: application/json\" \\\\ |\\n| > | -d \\'{ |\\n| > | \"id\": \"string\", |\\n| > | \"user\": \"string\" |\\n| > | }\\' |\\n```\\n\\n[Try it](/beta/api-reference/snap-ins/resources-post?explorer=true)\\n\\n200Successful\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | { |\\n| 2 | \"snap_in_version\": { |\\n| 3 | \"id\": \"string\", |\\n| 4 | \"display_id\": \"string\" |\\n| 5 | }, |\\n| 6 | \"event_sources\": {}, |\\n| 7 | \"inputs\": {}, |\\n| 8 | \"keyrings\": {} |\\n| 9 | }", + "title": "Resources Snap Ins (POST) | DevRev | Docs" }, { - "id": "ART-1175_KNOWLEDGE_NODE-0", - "text": "b'Getting started | DevRev | Docs\\n\\n[![]()![]()](https://developer.devrev.ai/)\\n\\nPublic\\n\\nPublic\\n\\nSearch\\n\\n`/`\\n\\nOn this page\\n\\n* [Prerequisites](/api-reference/getting-started#prerequisites)\\n* [Send your first API request](/api-reference/getting-started#send-your-first-api-request)\\n* [Making a GET request](/api-reference/getting-started#making-a-get-request)\\n* [Next steps](/api-reference/getting-started#next-steps)\\n\\n[API Reference](/api-reference/getting-started)\\n\\nGetting", - "title": "Getting started | DevRev | Docs" + "id": "ART-1213_KNOWLEDGE_NODE-0", + "text": "b'Get Rev Org | DevRev | Docs\\n\\n[![]()![]()](https://developer.devrev.ai/)\\n\\nPublic\\n\\nPublic\\n\\nSearch\\n\\n`/`\\n\\n[API Reference](/api-reference/getting-started)[rev-orgs](/api-reference/rev-orgs/workspaces)\\n\\nGet Rev Org\\n===========\\n\\nCopy page\\n\\nGET\\n\\nhttps://api.devrev.ai/rev-orgs.get\\n\\nGET\\n\\n/rev-orgs.get\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl https://api.devrev.ai/rev-orgs.get \\\\ |\\n| > | -H \"Authorization: Bearer \" |\\n```\\n\\n[Try", + "title": "Get Rev Org | DevRev | Docs" }, { - "id": "ART-4229_KNOWLEDGE_NODE-4", - "text": "[Events](https://devrev.ai/events)\\n * [News](https://devrev.ai/blog?category=news)\\n * [Case Studies](https://devrev.ai/case-study)\\n * [Documentation](https://docs.devrev.ai/)\\n * [API Reference](https://docs.devrev.ai/api/)\\n * [The Book of DevRev](https://thebook.devrev.ai/)\\n * [Partner Program](https://devrev.ai/partners)\\n * [Startup Program](https://devrev.ai/startups)\\n\\nCompany\\n\\n * [About](https://devrev.ai/about)\\n * [People](https://devrev.ai/people)\\n *", - "title": "API Changelog \u2014 DevRev | Docs" + "id": "ART-15292_KNOWLEDGE_NODE-1", + "text": "\"Content-Type: application/json\" \\\\ |\\n| > | -d \\'{ |\\n| > | \"owned_by\": [ |\\n| > | \"DEVU-12345\" |\\n| > | ], |\\n| > | \"resource\": {}, |\\n| > | \"title\": \"string\" |\\n| > | }\\' |\\n```\\n\\n[Try it](/api-reference/articles/create-article?explorer=true)\\n\\n201Created\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | { |\\n| 2 | \"article\": { |\\n| 3 | \"id\": \"string\", |\\n| 4 | \"owned_by\": [ |\\n| 5 | { |\\n| 6 | \"display_id\": \"string\", |\\n| 7 | \"id\": \"string\", |\\n| 8 | \"display_name\": \"string\", |\\n| 9 |", + "title": "Create Article | DevRev | Docs" }, { - "id": "ART-1980_KNOWLEDGE_NODE-29", - "text": "by customers through the Plug widget and customer portal.\\n\\nIn the Plug widget, articles are available in two places: the search bar and the Help section.\\n\\n**Search bar**\\n\\n![]()\\n\\n**Help section**\\n\\n![]()\\n\\nUsers can also view articles grouped into collections by visiting your help center hosted on your website. The visibility of collections and articles depends on the **Visible to** settings configured.\\n\\n[### Articles](/docs/product/articles)[###", - "title": "Knowledge Base | Computer for Support Teams | DevRev" + "id": "ART-1179_KNOWLEDGE_NODE-0", + "text": "b'List Artifacts | DevRev | Docs\\n\\n[![]()![]()](https://developer.devrev.ai/)\\n\\nPublic\\n\\nPublic\\n\\nSearch\\n\\n`/`\\n\\n[API Reference](/api-reference/getting-started)[artifacts](/api-reference/artifacts/attachments)\\n\\nList Artifacts\\n==============\\n\\nCopy page\\n\\nGET\\n\\nhttps://api.devrev.ai/artifacts.list\\n\\nGET\\n\\n/artifacts.list\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl https://api.devrev.ai/artifacts.list \\\\ |\\n| > | -H \"Authorization: Bearer \" |\\n```\\n\\n[Try", + "title": "List Artifacts | DevRev | Docs" }, { - "id": "ART-3194_KNOWLEDGE_NODE-10", - "text": "demo](https://devrev.ai/request-a-demo)\\n\\n[](https://devrev.ai)\\n\\n __\\n\\nProduct __\\n\\nPlatform __\\n\\nSolutions __\\n\\nMarketplace __\\n\\nCompany __\\n\\nResources __\\n\\n[Pricing](https://devrev.ai/pricing)\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](https://devrev.ai/request-a-demo)\\n\\n'", - "title": "API Changelog \u2014 DevRev | Docs" + "id": "ART-1177_KNOWLEDGE_NODE-0", + "text": "b'Get Artifact | DevRev | Docs\\n\\n[![]()![]()](https://developer.devrev.ai/)\\n\\nPublic\\n\\nPublic\\n\\nSearch\\n\\n`/`\\n\\n[API Reference](/api-reference/getting-started)[artifacts](/api-reference/artifacts/attachments)\\n\\nGet Artifact\\n============\\n\\nCopy page\\n\\nGET\\n\\nhttps://api.devrev.ai/artifacts.get\\n\\nGET\\n\\n/artifacts.get\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl -G https://api.devrev.ai/artifacts.get \\\\ |\\n| > | -H \"Authorization: Bearer \" \\\\ |\\n| > | -d id=ARTIFACT-12345", + "title": "Get Artifact | DevRev | Docs" }, { - "id": "ART-4980_KNOWLEDGE_NODE-7", - "text": "demo](https://devrev.ai/request-a-demo)\\n\\n[](https://devrev.ai)\\n\\n __\\n\\nProduct __\\n\\nPlatform __\\n\\nSolutions __\\n\\nMarketplace __\\n\\nCompany __\\n\\nResources __\\n\\n[Pricing](https://devrev.ai/pricing)\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](https://devrev.ai/request-a-demo)\\n\\n'", - "title": "API Changelog \u2014 DevRev | Docs" + "id": "ART-3191_KNOWLEDGE_NODE-18", + "text": "[`/artifacts.versions.prepare`](/public/api-reference/artifacts/versions-prepare) - Prepare artifact versions\\n\\n### Links\\n\\n* [`/links.replace`](/public/api-reference/links/replace) - Replace links\\n\\n### Metric Trackers\\n\\n* [`/metric-trackers.get`](/public/api-reference/slas/metric-trackers-get-post) - Get metric tracker details\\n\\nModified Endpoints\\n------------------\\n\\n### Accounts\\n\\nAdded `tier` filter support to:\\n\\n*", + "title": "Changelog | DevRev | Docs" } ] }, @@ -2244,54 +2244,54 @@ "query": "automations to fill repeated fields", "retrievals": [ { - "id": "ART-2016_KNOWLEDGE_NODE-9", - "text": "deduplication](/docs/automations/account-deduplication)\\n - [Airtable](/docs/automations/airtable)\\n - [Auto-link DevRev GitHub accounts](/docs/automations/auto-link-github-devrev)\\n - [Automatic customer reply](/docs/automations/auto-reply)\\n - [Auto parts to conversation](/docs/automations/auto-parts)\\n - [Automated part update](/docs/automations/automated-part-update)\\n - [Automate opportunities](/docs/automations/opportunity)\\n - [Bulk delete", - "title": "StageFlow automator | Automate | Snap-ins | DevRev" + "id": "ART-2007_KNOWLEDGE_NODE-24", + "text": "[Snap-ins](/docs/snapins)\\n[Automate](/docs/automate)\\n[Automate opportunities](/docs/automations/opportunity)\\n\\nAutomate opportunities\\n======================\\n\\nAutomate opportunities snap-in helps you automate the following features on opportunities to eliminate updating the fields manually and to enhance data consistency:\\n\\n* Auto-fills the forecast categories on the opportunities based on status updates. Enable this feature to keep the **Forecast Category** field on opportunities updated", + "title": "Automate opportunities | Automate | Snap-ins | DevRev" }, { - "id": "ART-2858_KNOWLEDGE_NODE-9", - "text": "deduplication](/docs/automations/account-deduplication)\\n - [Airtable](/docs/automations/airtable)\\n - [Auto-link DevRev GitHub accounts](/docs/automations/auto-link-github-devrev)\\n - [Automatic customer reply](/docs/automations/auto-reply)\\n - [Auto parts to conversation](/docs/automations/auto-parts)\\n - [Automated part update](/docs/automations/automated-part-update)\\n - [Automate opportunities](/docs/automations/opportunity)\\n - [Bulk delete", - "title": "Custom field migration | Automate | Snap-ins | DevRev" + "id": "ART-2007_KNOWLEDGE_NODE-26", + "text": "marketplace, find **Automate opportunities** and click **Install**.\\n\\nConfiguration\\n-------------\\n\\n1. To configure the snap-in, type /AutomateOpportunityConfig in the **Discussions** tab of the snap-in.\\n\\n![]()\\n\\n1. Fill the required fields and click **Submit**.\\n\\n[PreviousAutomated part update](/docs/automations/automated-part-update)[NextBulk delete data](/docs/automations/bulk-delete)\\n\\n#### On this page\\n\\n* [Installation](#installation)\\n*", + "title": "Automate opportunities | Automate | Snap-ins | DevRev" }, { - "id": "ART-2016_KNOWLEDGE_NODE-15", - "text": "[Custom field migration](/docs/automations/custom-field-migration)\\n - [Slack scraper](/docs/automations/slack-scraper)\\n - [Slack Broadcaster](/docs/automations/slack-broadcaster)\\n - [Reported by enricher](/docs/automations/ticket-reported-by)\\n - [Ticket approval workflow](/docs/automations/ticket-approval-workflow)\\n - [Ticket linked issues comment sync](/docs/automations/ticket-linked-issues-comment-sync)\\n - [Slack message agent](/docs/automations/slack-message-agent)\\n", - "title": "StageFlow automator | Automate | Snap-ins | DevRev" + "id": "ART-6175_KNOWLEDGE_NODE-24", + "text": "[Snap-ins](/docs/snapins)\\n[Automate](/docs/automate)\\n[Airtable](/docs/automations/airtable)\\n\\nAirtable\\n========\\n\\nThe **Airtable** snap-in automates lead intake from Airtable form submissions by mapping responses to DevRev contacts, accounts, and custom objects. It supports field mapping, duplicate detection, tagging, and ownership assignment using custom configurations. Submissions are processed in real time, enabling seamless CRM integration and streamlined data", + "title": "Airtable | Automate | Snap-ins | DevRev" }, { - "id": "ART-2016_KNOWLEDGE_NODE-10", - "text": "data](/docs/automations/bulk-delete)\\n - [Bulk work item uploader](/docs/automations/bulk-upload)\\n - [Commands surface expander](/docs/automations/commands-surface-expander)\\n - [Convergence](/docs/automations/converge)\\n - [Conversation reminder](/docs/automations/conversation-reminder)\\n - [CSAT on conversation](/docs/automations/csat-conv)\\n - [CSAT on ticket](/docs/automations/csat-tickets)\\n - [CSV work item uploader](/docs/automations/csv-work-item-uploader)\\n -", - "title": "StageFlow automator | Automate | Snap-ins | DevRev" + "id": "ART-2007_KNOWLEDGE_NODE-25", + "text": "in sync with their current stage, as per the stage to forecast category mapping configured in the automation.\\n* Auto-fills the **Probability** field on opportunities based on their current stage. Enable this feature to auto-update opportunity probabilities based on the stage to probability mapping configured in the automation.\\n\\nInstallation\\n------------\\n\\n1. In DevRev, go to **Settings** > **Snap-ins** and click **Explore Marketplace** in the top-right corner.\\n2. In the DevRev", + "title": "Automate opportunities | Automate | Snap-ins | DevRev" }, { - "id": "ART-2006_KNOWLEDGE_NODE-10", - "text": "data](/docs/automations/bulk-delete)\\n - [Bulk work item uploader](/docs/automations/bulk-upload)\\n - [Commands surface expander](/docs/automations/commands-surface-expander)\\n - [Convergence](/docs/automations/converge)\\n - [Conversation reminder](/docs/automations/conversation-reminder)\\n - [CSAT on conversation](/docs/automations/csat-conv)\\n - [CSAT on ticket](/docs/automations/csat-tickets)\\n - [CSV work item uploader](/docs/automations/csv-work-item-uploader)\\n -", - "title": "Automatic customer reply | Automate | Snap-ins | DevRev" + "id": "ART-2858_KNOWLEDGE_NODE-0", + "text": "b'Custom field migration | Automate | Snap-ins | DevRev\\n\\n* Computer\\n* Resources\\n* [Our Customers](/case-study)\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](/request-a-demo)\\n\\nComputer\\n\\nResources\\n\\n[Our Customers](/case-study)\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](/request-a-demo)\\n\\nSearch\\n\\n`CMD`\\xc2\\xa0+\\xc2\\xa0`K`\\n\\n* [Introduction](/docs)\\n* [Computer by DevRev](/docs/intro)\\n\\n + [Core concepts](/docs/product/core)\\n + [Apps](/docs/product/apps)\\n +", + "title": "Custom field migration | Automate | Snap-ins | DevRev" }, { - "id": "ART-2006_KNOWLEDGE_NODE-15", - "text": "[Custom field migration](/docs/automations/custom-field-migration)\\n - [Slack scraper](/docs/automations/slack-scraper)\\n - [Slack Broadcaster](/docs/automations/slack-broadcaster)\\n - [Reported by enricher](/docs/automations/ticket-reported-by)\\n - [Ticket approval workflow](/docs/automations/ticket-approval-workflow)\\n - [Ticket linked issues comment sync](/docs/automations/ticket-linked-issues-comment-sync)\\n - [Slack message agent](/docs/automations/slack-message-agent)\\n", - "title": "Automatic customer reply | Automate | Snap-ins | DevRev" + "id": "ART-1478_KNOWLEDGE_NODE-44", + "text": "2| - name: \\n 3| source: \\n 4| event_types: \\n 5| - timer.tick \\n 6| function: \\n[/code] \\n \\nThe payload contains the `metadata` fields you specified in the event source configuration. For example, `{\"event_key\": \"daily_events\"}` for the `daily-timer-source`.\\n\\n## Email-based event sources\\n\\nYou can create an email-based event source that can be used to write automations on top of emails. For this, a", + "title": "Event sources \u2014 DevRev | Docs" }, { - "id": "ART-2858_KNOWLEDGE_NODE-10", - "text": "data](/docs/automations/bulk-delete)\\n - [Bulk work item uploader](/docs/automations/bulk-upload)\\n - [Commands surface expander](/docs/automations/commands-surface-expander)\\n - [Convergence](/docs/automations/converge)\\n - [Conversation reminder](/docs/automations/conversation-reminder)\\n - [CSAT on conversation](/docs/automations/csat-conv)\\n - [CSAT on ticket](/docs/automations/csat-tickets)\\n - [CSV work item uploader](/docs/automations/csv-work-item-uploader)\\n -", - "title": "Custom field migration | Automate | Snap-ins | DevRev" + "id": "ART-2874_KNOWLEDGE_NODE-0", + "text": "b'Ticket issue field migrator | Automate | Snap-ins | DevRev\\n\\n* Computer\\n* Resources\\n* [Our Customers](/case-study)\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](/request-a-demo)\\n\\nComputer\\n\\nResources\\n\\n[Our Customers](/case-study)\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](/request-a-demo)\\n\\nSearch\\n\\n`CMD`\\xc2\\xa0+\\xc2\\xa0`K`\\n\\n* [Introduction](/docs)\\n* [Computer by DevRev](/docs/intro)\\n\\n + [Core concepts](/docs/product/core)\\n + [Apps](/docs/product/apps)\\n +", + "title": "Ticket issue field migrator | Automate | Snap-ins | DevRev" }, { - "id": "ART-2010_KNOWLEDGE_NODE-9", - "text": "deduplication](/docs/automations/account-deduplication)\\n - [Airtable](/docs/automations/airtable)\\n - [Auto-link DevRev GitHub accounts](/docs/automations/auto-link-github-devrev)\\n - [Automatic customer reply](/docs/automations/auto-reply)\\n - [Auto parts to conversation](/docs/automations/auto-parts)\\n - [Automated part update](/docs/automations/automated-part-update)\\n - [Automate opportunities](/docs/automations/opportunity)\\n - [Bulk delete", - "title": "Bulk work item uploader | Automate | Snap-ins | DevRev" + "id": "ART-3235_KNOWLEDGE_NODE-24", + "text": "[Snap-ins](/docs/snapins)\\n[Automate](/docs/automate)\\n[Reported by enricher](/docs/automations/ticket-reported-by)\\n\\nReported by enricher\\n====================\\n\\nThe [Reported by Enricher](https://marketplace.devrev.ai/ticket-reported-by) snap-in automatically updates the **Reported By** field on tickets created with an email entered in a custom field. It verifies if the email belongs to an existing customer of the configured account and either links to that customer or creates a new", + "title": "Reported by enricher | Automate | Snap-ins | DevRev" }, { - "id": "ART-2003_KNOWLEDGE_NODE-24", - "text": "deduplication](/docs/automations/account-deduplication)[### Airtable](/docs/automations/airtable)[### Auto-link DevRev GitHub accounts](/docs/automations/auto-link-github-devrev)[### Automatic customer reply](/docs/automations/auto-reply)[### Auto parts to conversation](/docs/automations/auto-parts)[### Automated part update](/docs/automations/automated-part-update)[### Automate opportunities](/docs/automations/opportunity)[### Bulk delete data](/docs/automations/bulk-delete)[### Bulk work item", - "title": "Automate | Snap-ins | DevRev" + "id": "ART-16803_KNOWLEDGE_NODE-9", + "text": "deduplication](/docs/automations/account-deduplication)\\n - [Airtable](/docs/automations/airtable)\\n - [Auto-link DevRev GitHub accounts](/docs/automations/auto-link-github-devrev)\\n - [Automatic customer reply](/docs/automations/auto-reply)\\n - [Auto parts to conversation](/docs/automations/auto-parts)\\n - [Automated part update](/docs/automations/automated-part-update)\\n - [Automate opportunities](/docs/automations/opportunity)\\n - [Bulk delete", + "title": "Workflow nodes | Workflows | Computer by DevRev | DevRev" }, { - "id": "ART-2007_KNOWLEDGE_NODE-15", - "text": "[Custom field migration](/docs/automations/custom-field-migration)\\n - [Slack scraper](/docs/automations/slack-scraper)\\n - [Slack Broadcaster](/docs/automations/slack-broadcaster)\\n - [Reported by enricher](/docs/automations/ticket-reported-by)\\n - [Ticket approval workflow](/docs/automations/ticket-approval-workflow)\\n - [Ticket linked issues comment sync](/docs/automations/ticket-linked-issues-comment-sync)\\n - [Slack message agent](/docs/automations/slack-message-agent)\\n", - "title": "Automate opportunities | Automate | Snap-ins | DevRev" + "id": "ART-4215_KNOWLEDGE_NODE-9", + "text": "deduplication](/docs/automations/account-deduplication)\\n - [Airtable](/docs/automations/airtable)\\n - [Auto-link DevRev GitHub accounts](/docs/automations/auto-link-github-devrev)\\n - [Automatic customer reply](/docs/automations/auto-reply)\\n - [Auto parts to conversation](/docs/automations/auto-parts)\\n - [Automated part update](/docs/automations/automated-part-update)\\n - [Automate opportunities](/docs/automations/opportunity)\\n - [Bulk delete", + "title": "Notion AirSync | AirSync | Snap-ins | DevRev" } ] }, @@ -2300,54 +2300,54 @@ "query": "action to reopen ticket in workflow", "retrievals": [ { - "id": "ART-1961_KNOWLEDGE_NODE-37", - "text": "\\n{{Ticket\\xc2\\xa0Created\\xc2\\xa0>\\xc2\\xa0Output\\xc2\\xa0>\\xc2\\xa0Reported\\xc2\\xa0By\\xc2\\xa0>\\xc2\\xa0Rev\\xc2\\xa0Org\\xc2\\xa0>\\xc2\\xa0Display\\xc2\\xa0Name}}.\\xe2\\x80\\x9d\\n\\n\\n\\nDelay\\n\\n\\n\\nDuration: 2 minutes\\n\\n\\n\\nIf-else\\n\\n\\n\\nAttribute:\\xc2\\xa0Ticket\\xc2\\xa0Created/Output\\xc2\\xa0>\\xc2\\xa0Applies\\xc2\\xa0to\\xc2\\xa0part\\xc2\\xa0>\\xc2\\xa0Display\\xc2\\xa0ID \\nOperator: Equals \\nOperand: CAPL-18\\n\\n\\n\\nTicket \\ncreated\\n\\n\\n\\nEnd\\n```\\n\\n[### Workflow action", + "id": "ART-1961_KNOWLEDGE_NODE-35", + "text": "or one from a previous node.\\n8. Click **Deploy**.\\n9. If you need to modify the workflow after is has been deployed, click **Pause**, edit the workflow, then click **Deploy** to reactivate it.\\n\\nWorkflow example: Ticket auto-response\\n--------------------------------------\\n\\n```\\nControl\\n\\n\\n\\nIf true\\n\\n\\n\\nAction\\n\\n\\n\\nAction\\n\\n\\n\\nIf false\\n\\n\\n\\nAdd comment\\n\\n\\n\\nObject:\\xc2\\xa0Ticket\\xc2\\xa0Created\\xc2\\xa0>\\xc2\\xa0Output\\xc2\\xa0>\\xc2\\xa0ID \\nVisibility: External \\nBody:", "title": "Workflows | Computer by DevRev | DevRev" }, { - "id": "ART-2012_KNOWLEDGE_NODE-28", - "text": "say \\xe2\\x80\\x9cI would like to add a terminal stage on my tickets\\xe2\\x80\\x9d and we will get it done.\\n\\n * If no terminal stage is set, tickets will reopen on new comments from customers if **Reopen Closed Tickets on customer message** is enabled in the [convergence snap-in](./converge). The tickets move to the _In Progress_ state by default.\\n\\n * If you connected your support email address with DevRev, it is recommended that you enable the **Allow automations to send email** in your", - "title": "Follow-up ticket | Automate | Snap-ins | DevRev" + "id": "ART-16803_KNOWLEDGE_NODE-26", + "text": "Tickets\\n* Meetings\\n* Objects linked to issues\\n* Users\\n\\nTo configure a workspace object loop:\\n\\n1. On the **workflow canvas**, add an action step named **Loop for [Object]**, where [Object] is the entity you want to iterate over.\\n2. Apply **filter conditions** to refine the set of objects included in the loop and perform operations on them.\\n\\nAll **actions** inside the loop execute once per object that satisfies the filter conditions.\\n\\n### For Each\\n\\nThe **For Each** loop iterates", + "title": "Workflow nodes | Workflows | Computer by DevRev | DevRev" }, { - "id": "ART-1961_KNOWLEDGE_NODE-35", - "text": "or one from a previous node.\\n8. Click **Deploy**.\\n9. If you need to modify the workflow after is has been deployed, click **Pause**, edit the workflow, then click **Deploy** to reactivate it.\\n\\nWorkflow example: Ticket auto-response\\n--------------------------------------\\n\\n```\\nControl\\n\\n\\n\\nIf true\\n\\n\\n\\nAction\\n\\n\\n\\nAction\\n\\n\\n\\nIf false\\n\\n\\n\\nAdd comment\\n\\n\\n\\nObject:\\xc2\\xa0Ticket\\xc2\\xa0Created\\xc2\\xa0>\\xc2\\xa0Output\\xc2\\xa0>\\xc2\\xa0ID \\nVisibility: External \\nBody:", + "id": "ART-1961_KNOWLEDGE_NODE-30", + "text": "Action: Tasks that modify one or more objects in the system.\\n* Control: Conditional (if-then) blocks to determine which actions to take based on an operand (variable) and an operator.\\n* Delay: Wait to take an action.\\n\\nAI nodes\\n--------\\n\\nWe provide several native AI nodes out of the box to enhance your workflows.\\n\\n**Spam checker**\\n\\nThe spam checker takes the ID of a ticket or object and determines whether the ticket or conversation is spam. You can use this output in your workflows as", "title": "Workflows | Computer by DevRev | DevRev" }, { - "id": "ART-12390_KNOWLEDGE_NODE-29", - "text": "Ticket | Creates a new ticket in DevRev. | * Ticket details like title, body, applies\\\\_to\\\\_part, etc. * subtype: (Optional) Ticket subtype * apps: (Optional) Related apps * app\\\\_custom\\\\_fields: (Optional) Custom fields | Created ticket object |\\n| Convert Conversation To Ticket | Converts a conversation to a ticket. | * conversation\\\\_id: ID of the conversation to convert | ticket\\\\_id: ID of the created ticket |\\n\\nObject retrieval\\n----------------\\n\\n| Operation | Description | Input", - "title": "Workflow action library | Workflows | Computer by DevRev | DevRev" + "id": "ART-12391_KNOWLEDGE_NODE-27", + "text": "workflow.\\n\\nNow, your workflow runs whenever a conversation or a ticket gets created and it\\nassigns it to an AI agent, which handles the conversation. No brittle rules.\\n\\nFind below a detailed explanation of all the fields needed to configure in the\\n\"Talk to Agent\" Step\\n\\n| Parameter | Type | Description |\\n| --- | --- | --- |\\n| agent | String | ID of the AI agent to use. Use the dropdown to select one. |\\n| object | String | ID of the conversation or ticket where the agent operate.s |\\n|", + "title": "Conversational workflows | Workflows | Computer by DevRev | DevRev" }, { - "id": "ART-2012_KNOWLEDGE_NODE-25", - "text": "following stages under the _Closed_ state: _Resolved_ , _Archived_ , _Accepted_ , _Canceled_. _Archived_ is the terminal stage. Now if a customer sends a new email or adds a new comment on the archived ticket from the customer portal, the archived ticket remains archived and a follow-up ticket is created. A message is added to the archived ticket automatically based on your configuration. The follow-up ticket will have the reference of the archived ticket in the first message so that your", - "title": "Follow-up ticket | Automate | Snap-ins | DevRev" + "id": "ART-2024_KNOWLEDGE_NODE-25", + "text": "integrates into your workflow, regardless of whether you\\'re engaged in customer support interactions or immersed in building projects.\\n\\nCommands\\n--------\\n\\nSlash commands are available through text fields such as:\\n\\n* **Inbox** > **Conversation** > **Customer chat/Discussions**\\n* **Tickets** > **Customer chat/Discussions**\\n* **Issues** > **Discussions**\\n\\nEntering / in a text field allows you to execute commands, revealing a comprehensive list of available options. Respond to customers", + "title": "Slash commands | Automate | Snap-ins | DevRev" }, { - "id": "ART-1979_KNOWLEDGE_NODE-48", - "text": "engineer can directly close and cancel such tickets.\\n* *Accepted* (A)\\n\\n The ticket requires a new feature development on the platform for resolution. However, there is no active work on the ticket but the feature addition required to meet the ticket will be done in the future. This stage is added to ensure that feature requests do not linger in the APA queue and to ensure that the right features are prioritized during roadmap planning.\\n* *Resolved* (R)\\n\\n The goal target stage for", - "title": "Tickets | Computer for Support Teams | DevRev" + "id": "ART-1961_KNOWLEDGE_NODE-33", + "text": "account.\\n\\n**Ask AI**\\n\\nWrite your own LLM prompt to generate content that can be used in various contexts. For example, you can request a summary of a ticket based on the title and description.\\n\\nCreating a workflow\\n-------------------\\n\\n1. Go to [**Settings** > **Workflows**](https://app.devrev.ai/devrev/settings/workflows?labels=skill&labelsOp=not_any&status=active). A canvas appears.\\n2. Enter a name for your workflow.\\n3. Select the steps you want to include by selecting them from the", + "title": "Workflows | Computer by DevRev | DevRev" }, { - "id": "ART-2012_KNOWLEDGE_NODE-24", - "text": "customer comments on permanently closed tickets. It allows you to configure the time after which a ticket stage should be marked as closed and creates a new follow-up ticket along with all the attachments and a custom message to let the customers know that the ticket is permanently closed automatically if required.\\n\\nFor more information, refer to the [Follow-up ticket snap-in](https://marketplace.devrev.ai/followup?) on the DevRev marketplace.\\n\\nLet\\xe2\\x80\\x99s say your ticket has the", - "title": "Follow-up ticket | Automate | Snap-ins | DevRev" + "id": "ART-2048_KNOWLEDGE_NODE-27", + "text": "allows you to create parent/child relationships between issues, you cannot do the same with tickets. If your workflow requires manual creation of parent/child relationships in DevRev work items, you should use issues. If that is not a requirement and tickets are preferred for another reason, you can specify tickets as the target for ClickUp tasks.\\n\\nImport from ClickUp\\n-------------------\\n\\nFollow the steps below to import from ClickUp:\\n\\n1. In **Marketplace**, search for **ClickUp** and", + "title": "ClickUp AirSync | AirSync | Snap-ins | DevRev" }, { - "id": "ART-1979_KNOWLEDGE_NODE-41", - "text": "progress\\n\\n\\n\\nOpen\\n\\n\\n\\nEscalate\\n\\n\\n\\nValidate the fix\\n\\n\\n\\nAdditional detail needed\\n\\n\\n\\nCustomer responds\\n\\n\\n\\nStart\\n\\n\\n\\nFeature request accepted\\n\\n\\n\\nResolved\\n\\n\\n\\nNot valid\\n\\n\\n\\nQueued\\n\\n\\n\\nWork in progress\\n\\n\\n\\nAwaiting product assist\\n\\n\\n\\nAwaiting development\\n\\n\\n\\nAwating customer response\\n\\n\\n\\nIn development\\n\\n\\n\\nAccepted\\n\\n\\n\\nResolved\\n\\n\\n\\nCanceled\\n```\\n\\n**Open**\\n\\n* *Queued* (Q)\\n The initial stage for all tickets. When a new ticket is created,", - "title": "Tickets | Computer for Support Teams | DevRev" + "id": "ART-1275_KNOWLEDGE_NODE-12", + "text": "`src/functions/ticket_creator/index.test.ts`\\n\\n[4](/snapin-development/tutorials/timer-ticket-creator#event-received-by-the-snap-in-function)\\n\\n### Event received by the snap-in function\\n\\nIn the hello-world snap-in, the ID of the created work-item gets extracted from\\nthe input event as such.\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | console.info( |\\n| 2 | `The work ${events[0].payload.work_created.work.id} has been created.` |\\n| 3 | ); |\\n```\\n\\nThe schema for a event received by the snap-in", + "title": "Using a snap-in to perform a DevRev action | DevRev | Docs" }, { - "id": "ART-1961_KNOWLEDGE_NODE-31", - "text": "needed. For example, if the ticket is found to be spam, you can automatically add a comment to the ticket.\\n\\n**Suggest part**\\n\\nOften, your integrations create tickets or issues associated with a default part. The suggest part takes the ID of a ticket or issue and suggests a relevant part. You can use this to route your tickets or issues to the most appropriate part of the product. For example, when a ticket is created, you can find a relevant part and update the ticket with the suggested", - "title": "Workflows | Computer by DevRev | DevRev" + "id": "ART-1997_KNOWLEDGE_NODE-29", + "text": "workflows\\xe2\\x80\\x94such as creating tickets, conversations, and SLAs\\xe2\\x80\\x94are linked to workspaces.\\n\\n\\xf0\\x9f\\x92\\xa1 Opportunity\\n-------------\\n\\nAn opportunity record represents a potential source of revenue for your organization. Opportunities feature customizable states and stages that communicate their position within the sales pipeline.\\n\\nIf an account has multiple sales opportunities, you can connect multiple opportunities to it. You can also associate tickets with", + "title": "Computer for Growth Teams | DevRev" }, { - "id": "ART-12390_KNOWLEDGE_NODE-39", - "text": "to update * subtype: (Optional) Ticket subtype * apps: (Optional) Related apps * app\\\\_custom\\\\_fields: (Optional) Custom fields * stage: (Optional) New stage | Updated ticket object |\\n\\nObject links\\n------------\\n\\n| Operation | Description | Input Parameters | Output |\\n| --- | --- | --- | --- |\\n| LinkConversationWithTicket | Creates a link between a conversation and a ticket. | * source: Conversation ID * link\\\\_type: Type of link (usually \"is\\\\_related\\\\_to\") * target: Ticket ID | Empty", - "title": "Workflow action library | Workflows | Computer by DevRev | DevRev" + "id": "ART-1645_KNOWLEDGE_NODE-5", + "text": "organization\\xe2\\x80\\x99s unique workflows and reporting needs. By using the customization framework, you can extend these objects with custom fields that reflect your processes.\\n\\nThis section provides an overview of the customization framework and walks you through the process of tracking bugs in your organization. By the end of this section, you\\xe2\\x80\\x99ll be able to:\\n\\n 1. Customize DevRev objects such as _issue_ and _ticket_ by adding custom fields.\\n 2. Override default field", + "title": "Object customization (Beta) \u2014 DevRev | Docs" } ] }, @@ -2356,54 +2356,54 @@ "query": "assign issue owner to someone else using workflow", "retrievals": [ { - "id": "ART-1981_KNOWLEDGE_NODE-30", - "text": "conversation of which you are not the owner, let the owner know to respond. It's beneficial to retain the same point of contact for the duration of the conversation unless the owner refers some another user.\\n* If the conversation has a customer org that's unidentified or is new, add yourself (the customer experience engineer) as the owner of the ticket. Try to find the appropriate owner for the customer org and update the customer record accordingly.\\n* Change the stage of the conversation to", - "title": "Support best practices | Computer for Support Teams | DevRev" + "id": "ART-15487_KNOWLEDGE_NODE-11", + "text": "|\\n| > | }, |\\n| > | { |\\n| > | \"name\": \"rca\", |\\n| > | \"field_type\": \"rich_text\", |\\n| > | \"ui\": { |\\n| > | \"display_name\": \"RCA\", |\\n| > | } |\\n| > | }, |\\n| > | ] |\\n| > | }\\' |\\n```\\n\\n##### \\n\\nA bug has been identified in the production environment. The reporter creates a\\n*bug*-flavored *issue* object to track it and assigns a relevant owner.\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl --location \\'https://api.devrev.ai/works.create\\' \\\\ |\\n| > | --header \\'Content-Type:", + "title": "Object customization | DevRev | Docs" }, { - "id": "ART-2737_KNOWLEDGE_NODE-24", - "text": "issue creator](/docs/automations/smart-issue-creator)\\n\\nSmart issue creator\\n===================\\n\\nThe Smart issue creator snap-in generates an issue from a ticket when /smart\\\\_issue\\\\_create is entered in the **Discussions** section of a ticket. Additionally, it updates the target close date to match the sprint end date whenever the sprint field is updated in an issue.\\n\\n![]()\\n\\nFor more information, refer to the\\n[Smart issue creator", - "title": "Smart issue creator | Automate | Snap-ins | DevRev" + "id": "ART-1994_KNOWLEDGE_NODE-33", + "text": "sprint board and click **+Issue**.\\n Create a new issue, assign it to the part, sprint and add the owner.\\n\\n ![]()\\n\\n Sprints are not coordinated with stages.\\n3. Select issues that you would like to assign to **Sprint 1** or **Sprint 2** then click **Move** in the toolbar at the top of the screen and select the sprint.\\n\\n ![]()\\n4. Go to **Sprint 1** or **Sprint 2** to see that issues are displayed.\\n\\n ![]()\\n\\n The sprint is also displayed in (and can be changed from) the", + "title": "Sprint mode | Computer for Builders | DevRev" }, { - "id": "ART-1992_KNOWLEDGE_NODE-31", - "text": "on the top right corner of your screen.\\n3. Add a title and description for your new issue. You can also attach files related to the issue in the description.\\n4. Select which part of the company/product this issue is related to.\\n\\n ![]()\\n5. Enter other attributes for the issue: change the assignee or accept the default; enter the severity; add any relevant tags to help employees identify any relevant traits of the issue; select the workspace that the issue pertains to.\\n6. If there are", - "title": "Issues | Computer for Builders | DevRev" + "id": "ART-2737_KNOWLEDGE_NODE-25", + "text": "snap-in](https://marketplace.devrev.ai/smart-issue-creator) on the DevRev marketplace.\\n\\nInstallation\\n------------\\n\\n1. In DevRev, go to **Settings** > **Snap-ins** and click **Explore Marketplace** in the top-right corner.\\n2. In the DevRev marketplace, find **Smart issue creator** and click **Install**.\\n3. In DevRev, **Snap-ins** > **Smart issue creator** > **Configure**.\\n4. Select the default owner, part, and tags. The default owner is assigned if no owner is selected from the snapkit.", + "title": "Smart issue creator | Automate | Snap-ins | DevRev" }, { - "id": "ART-1992_KNOWLEDGE_NODE-29", - "text": "an issue, you can create a parent issue or a child issue. In an issue, select **Link Issues** in the **Issues** pane and select the type to add.\\n\\n![]()\\n\\n![]()\\n\\nWhile a parent issue can and usually does have multiple children, an issue can have only one parent. If you try to add a parent to an issue that already has one, it fails.\\n\\n[Tasks](./tasks) can be used to break an issue down into smaller pieces. Issues may involve a checklist of items to be handled that can be represented as", - "title": "Issues | Computer for Builders | DevRev" + "id": "ART-2053_KNOWLEDGE_NODE-56", + "text": "they do not match 1 to 1. The stages can still be mapped - for example Done in Jira to Completed in DevRev etc.\\n\\n![]()\\n\\nFor Jira Data Center, workflow extraction captures statuses but not transitions. This means that in DevRev all transitions are permitted. This can be edited manually in DevRev.\\n\\n### Recommended permissions for syncing to Jira\\n\\nThe following are self-explanatory and are usually enabled by default: assign issues, edit issues, transition issues, close issues, link issues,", + "title": "Jira Software AirSync | AirSync | Snap-ins | DevRev" }, { - "id": "ART-2010_KNOWLEDGE_NODE-28", - "text": "user ID mentioned in a row doesn\\'t exist. Other work items aren\\'t impacted by this.\\n* The workspace ID is only used for associating tickets to the workspace and not issues.\\n* If the CSV lists multiple owners, only the first is set as the owner in the DevRev work item.\\n\\nHow to use bulk ticket uploader\\n-------------------------------\\n\\n1. In the **Discussion** tab of an account, ticket, part, or issue, enter /upload\\\\_workitems.\\n A **Bulk Uploader Bot** form appears.\\n2. From the", - "title": "Bulk work item uploader | Automate | Snap-ins | DevRev" + "id": "ART-16355_KNOWLEDGE_NODE-26", + "text": "**Reported\\\\_by,** and **Contact** columns, provide the email of the person to be assigned as the owner or reporter of the work item. If the CSV lists multiple owners, only the first will be set as the owner.\\n* For the **Applies to Part**, **Stage**, **Account**, **Developed with Parts**, and **Tags** columns, provide the part name, stage name, account name, part name, and tag name respectively as it is present in the UI, ensuring case sensitivity.\\n* For **Date** and **Timestamp** related", + "title": "CSV commands uploader | Automate | Snap-ins | DevRev" }, { - "id": "ART-4022_KNOWLEDGE_NODE-27", - "text": "person who should be assigned as the owner or reporter of the work item. If the CSV lists multiple owners, only the first is set as the owner.\\n2. For Applies to Part, Stage, Account, RevOrg, Developed with Parts, and Tags columns, provide the part name, stage name, account name, workspace, part name, and tag name respectively as it appears in the UI (case-sensitive).\\n3. For Date and Timestamp related fields, provide the date and timestamp in the format YYYY/MM/DD.\\n4. The tnt\\\\_\\\\_ prefix in", - "title": "CSV work item uploader | Automate | Snap-ins | DevRev" + "id": "ART-15716_KNOWLEDGE_NODE-32", + "text": "issues, or custom objects) is supported via the DevRev API.\\n\\nYou can use the API to create, update, or reorder stages in your workflow.\\n\\nThe endpoint and payload depend on the object type (ticket, issue, custom object, etc.).\\n\\nIf you share which object\\xe2\\x80\\x99s stages you want to customize, I can provide a sample API call or payload.Analytics and Reporting\\n\\n1. Creating Reports in DevRev\\n\\nYou can create reports in DevRev by building dashboards with widgets:\\n\\nGo to the Vista you", + "title": "Support queries related playbook" }, { - "id": "ART-12394_KNOWLEDGE_NODE-13", - "text": "creator](/docs/automations/smart-issue-creator)\\n - [Set user preference for group](/docs/automations/set-user-preference)\\n - [SLA status change Slack notifier](/docs/automations/sla-change-notifier)\\n - [Slash commands](/docs/automations/slash-commands)\\n - [Spam Shield](/docs/automations/spam-shield)\\n - [Subtype Migration](/docs/automations/subtype-migration)\\n - [Ticket age in engineering](/docs/automations/ticket-age-in-engineering)\\n - [Ticket issue field", - "title": "Workflow management | Workflows | Computer by DevRev | DevRev" + "id": "ART-16803_KNOWLEDGE_NODE-26", + "text": "Tickets\\n* Meetings\\n* Objects linked to issues\\n* Users\\n\\nTo configure a workspace object loop:\\n\\n1. On the **workflow canvas**, add an action step named **Loop for [Object]**, where [Object] is the entity you want to iterate over.\\n2. Apply **filter conditions** to refine the set of objects included in the loop and perform operations on them.\\n\\nAll **actions** inside the loop execute once per object that satisfies the filter conditions.\\n\\n### For Each\\n\\nThe **For Each** loop iterates", + "title": "Workflow nodes | Workflows | Computer by DevRev | DevRev" }, { - "id": "ART-2737_KNOWLEDGE_NODE-25", - "text": "snap-in](https://marketplace.devrev.ai/smart-issue-creator) on the DevRev marketplace.\\n\\nInstallation\\n------------\\n\\n1. In DevRev, go to **Settings** > **Snap-ins** and click **Explore Marketplace** in the top-right corner.\\n2. In the DevRev marketplace, find **Smart issue creator** and click **Install**.\\n3. In DevRev, **Snap-ins** > **Smart issue creator** > **Configure**.\\n4. Select the default owner, part, and tags. The default owner is assigned if no owner is selected from the snapkit.", - "title": "Smart issue creator | Automate | Snap-ins | DevRev" + "id": "ART-16615_KNOWLEDGE_NODE-25", + "text": "work items through different stages of completion. It's particularly valuable for process-oriented workflows, such as moving tickets through support stages, tracking issues from development to deployment, or managing sales opportunities through pipeline stages.\\n\\nHow to use it\\n-------------\\n\\n### Set up your board\\n\\n1. **Access the view**: Go to any work item list, such as Issues or Tickets, and select **Board View** from the view type selector\\n2. **Configure columns**: Click the", + "title": "Board view | Vistas | Computer by DevRev | DevRev" }, { - "id": "ART-1645_KNOWLEDGE_NODE-13", - "text": ">| }, \\n >| ] \\n >| }\\'\\n[/code] \\n \\n#####\\n\\nA bug has been identified in the production environment. The reporter creates a _bug_ -flavored _issue_ object to track it and assigns a relevant owner.\\n\\n[code]\\n\\n $| curl --location \\'https://api.devrev.ai/works.create\\' \\\\ \\n ---|--- \\n >| --header \\'Content-Type: application/json\\' \\\\ \\n >| --header \\'Authorization: Bearer \\' \\\\ \\n >| --data \\'{ \\n >| \"type\": \"issue\", \\n >|", - "title": "Object customization (Beta) \u2014 DevRev | Docs" + "id": "ART-1992_KNOWLEDGE_NODE-36", + "text": "Development* depending on the current priority and bandwidth.\\n* *Prioritized*\\n\\n Issues that are planned to be completed in the current or subsequent development cycle but which have not yet been started. Issues in the *prioritized* stage should have clear requirements. Issues in the *Prioritized* stage may be taken up for execution (promoted to *In development*) or deprioritized (demoted to *Backlog*).\\n\\n**In-progress**\\n\\n* *In development*\\n\\n The issue owner is actively working on the", + "title": "Issues | Computer for Builders | DevRev" }, { - "id": "ART-1951_KNOWLEDGE_NODE-27", - "text": "work record can be assigned to others.\\n\\n![]()\\n\\nUse child issues and dependency issues for more heavy work assignments to others that are related to your work. Use tasks only for lightweight things like reviewing your work.\\n\\nYou cannot see the linked work item (issue, ticket, or opportunity) for a task and can navigate to it directly from there.\\n\\n[PreviousBoard view](/docs/product/board-view)[NextUpdates](/docs/product/updates)\\n\\n[Enterprise grade security to protect customer", - "title": "Tasks | Computer by DevRev | DevRev" + "id": "ART-2048_KNOWLEDGE_NODE-27", + "text": "allows you to create parent/child relationships between issues, you cannot do the same with tickets. If your workflow requires manual creation of parent/child relationships in DevRev work items, you should use issues. If that is not a requirement and tickets are preferred for another reason, you can specify tickets as the target for ClickUp tasks.\\n\\nImport from ClickUp\\n-------------------\\n\\nFollow the steps below to import from ClickUp:\\n\\n1. In **Marketplace**, search for **ClickUp** and", + "title": "ClickUp AirSync | AirSync | Snap-ins | DevRev" } ] }, @@ -2412,54 +2412,54 @@ "query": "add multiple email addresses to one contact through Grow interface", "retrievals": [ { - "id": "ART-2032_KNOWLEDGE_NODE-31", - "text": "creators. Enter multiple emails separated by commas.\\n * **Add non-existing customers**: Enable this to allow people in meetings who are not already customers to be added as customers.\\n\\nIf a meeting is scheduled with people who are neither part of the company nor existing customers, this option allows them to be added as customers.\\n\\n* **Track meetings from free email domains**: Enable this feature to capture meetings scheduled using non-work email addresses, such as gmail.com or", - "title": "Google Calendar | Integrate | Snap-ins | DevRev" + "id": "ART-16784_KNOWLEDGE_NODE-6", + "text": "in the source system.\\n\\nTerms related to connection: AirSync, snap-incontact\\n\\nIndividual prospects or users associated with an organization\\'s workspaces or accounts.\\n\\nContacts can be associated with an account or workspace, but not always.\\n\\nTerms related to contact: account, workspace\\n\\nRead more about contact: [https://devrev.ai/docs/product/grow](https://devrev.ai/docs/product/grow)conversation\\n\\nAn interaction between the builder and consumer that may be escalated to a", + "title": "Glossary" }, { - "id": "ART-2002_KNOWLEDGE_NODE-27", - "text": "Plug, email, and WhatsApp) can be matched to the right customer record.\\n\\n![]()\\n\\nYou can create a contact using DevRev's rev-users.create API. Follow the [Create accounts and contacts in DevRev](https://developer.devrev.ai/beta/guides/create-accounts-and-contacts-in-dev-rev) tutorial.\\n\\n### Bulk import customer records\\n\\nTo bulk import customer records, see [Account and contact import](/docs/product/account-contact-import).\\n\\nYou can also use [AirSync](https://docs.devrev.ai/import) to", - "title": "Contacts | Computer for Growth Teams | DevRev" + "id": "ART-2575_KNOWLEDGE_NODE-28", + "text": "a database identifier or an email address.)\\n* account\\\\_external\\\\_reference (the external reference of the contact\\'s parent account)\\n\\n### Array fields\\n\\nFor fields that accept multiple values, such as **owners** and **industry**, values should be separated by commas (,). For example, Agriculture and Forestry should be written as Agriculture,Forestry.\\n\\n![]()\\n\\nIf a value contains a comma, enclose it in backticks. For example, enter \"Rail, Bus & Taxi\" as `Rail, Bus & Taxi`.\\n\\n###", + "title": "Account and contact import | Computer for Growth Teams | DevRev" }, { - "id": "ART-2002_KNOWLEDGE_NODE-28", - "text": "migrate your customer contacts from various platforms such as Hubspot, Salesforce, Zendesk, Jira, Linear, ServiceNow and more.\\n\\nCustomer records offer a place to do the following:\\n\\n* Find all conversations and tickets linked to a customer in one view.\\n* Have internal discussions related to a customer.\\n* Add description or notes about a customer.\\n* Assign an owner or tags to the customer.\\n\\n![]()\\n\\nApart from customer records that get automatically created from your [Plug", - "title": "Contacts | Computer for Growth Teams | DevRev" + "id": "ART-1284_KNOWLEDGE_NODE-45", + "text": "12 | \"inReplyToId\": { |\\n| 13 | \"stringValues\": [ |\\n| 14 | \"jksdnfjnsflkdsfkjaabcdefghiuK8BA@mail.gmail.com\" |\\n| 15 | ] |\\n| 16 | }, |\\n| 17 | \"messageId\": \"ABCdEfghijklmnopqrstuvwZHL+AB_XYZg@mail.gmail.com\", |\\n| 18 | \"rawBodyartifactId\": \"don:core:dvrv-us-1:devo/802:artifact/296\", |\\n| 19 | \"referenceIds\": { |\\n| 20 | \"stringValues\": [ |\\n| 21 | \"abcdabc123123123@mail.gmail.com\" |\\n| 22 | ] |\\n| 23 | }, |\\n| 24 | \"artifactIds\": [ |\\n| 25 | \"don:core:dvrv-us-1:devo/802:artifact/1\" |\\n| 26 |", + "title": "Event sources | DevRev | Docs" }, { - "id": "ART-2575_KNOWLEDGE_NODE-32", - "text": "required headers | Include headers for the required fields in the CSV. |\\n\\n[PreviousContacts](/docs/product/customers)[NextGrow snap-ins](/docs/product/snapins-grow)\\n\\n#### On this page\\n\\n* [Import data](#import-data)\\n* [CSV file requirements](#csv-file-requirements)\\n* [Mandatory fields](#mandatory-fields)\\n* [Array fields](#array-fields)\\n* [Tags](#tags)\\n* [Owner fields](#owner-fields)\\n* [Limitations](#limitations)\\n* [Troubleshooting](#troubleshooting)\\n\\n[Enterprise grade security to", - "title": "Account and contact import | Computer for Growth Teams | DevRev" + "id": "ART-980_KNOWLEDGE_NODE-24", + "text": "Email integration\\n Support Portal\\n \\n \\n Operate App\\n Grow App\\n \\n Account Management\\n Contact Management\\n Engagement Tracking\\n \\n \\n Core Services\\n Marketplace\\n \\n Partnerships\\n Integrations\\n \\n Discord\\n Slack\\n DevRev CLI\\n KB Extraction\\n Github Airdrop\\n SFDC Airdrop\\n", + "title": "How to Think About (And Structure) Your Products" }, { - "id": "ART-2575_KNOWLEDGE_NODE-8", - "text": "options](/docs/plug/session-recording)\\n - [Cross-domain session tracking](/docs/plug/cross-domain-session)\\n + [Nudges](/docs/plug/nudges)\\n* [Computer for Growth Teams](/docs/product/grow)\\n\\n + [Accounts](/docs/product/account)\\n + [Opportunities](/docs/product/opportunity)\\n + [Contacts](/docs/product/customers)\\n + [Account and contact import](/docs/product/account-contact-import)\\n + [Grow snap-ins](/docs/product/snapins-grow)\\n* [Snap-ins](/docs/snapins)\\n\\n +", - "title": "Account and contact import | Computer for Growth Teams | DevRev" + "id": "ART-2045_KNOWLEDGE_NODE-51", + "text": "email: [a@example.com](mailto:a@example.com) account: **None** | email: [a@example.com](mailto:a@example.com) account: **None** | Existing contact used |\\n| email: [a@example.com](mailto:a@example.com) account: \"Example\" | email: [a@example.com](mailto:a@example.com) account: \"Example\" | Existing contact used |\\n| email: [a@example.com](mailto:a@example.com) account: \"Example\" | email: [a@example.com](mailto:a@example.com) account: **None** | New contact created |\\n| email:", + "title": "AirSync | Snap-ins | DevRev" }, { - "id": "ART-2002_KNOWLEDGE_NODE-8", - "text": "tracking](/docs/plug/cross-domain-session)\\n + [Nudges](/docs/plug/nudges)\\n* [Computer for Growth Teams](/docs/product/grow)\\n\\n + [Accounts](/docs/product/account)\\n + [Opportunities](/docs/product/opportunity)\\n + [Contacts](/docs/product/customers)\\n + [Account and contact import](/docs/product/account-contact-import)\\n + [Grow snap-ins](/docs/product/snapins-grow)\\n* [Snap-ins](/docs/snapins)\\n\\n + [Automate](/docs/automate)\\n\\n - [Account", - "title": "Contacts | Computer for Growth Teams | DevRev" + "id": "ART-1960_KNOWLEDGE_NODE-28", + "text": "Individual prospects or users associated with an organization\\'s workspaces or accounts.\\n: Contacts can be associated with an account or workspace, but not always.\\n: Terms related to\\xc2\\xa0*contact*:\\n\\n * *[account](#account)*\\n * *[workspace](#workspace)*\\n: Read more about\\xc2\\xa0[*contact*](https://docs.devrev.ai/product/grow)\\n\\nconversation\\n\\n: An interaction between the builder and consumer that may be escalated to a ticket.\\n: Terms related", + "title": "Glossary | Computer by DevRev | DevRev" }, { - "id": "ART-2575_KNOWLEDGE_NODE-17", - "text": "* [Email snap-in configuration](/docs/integrations/email-config)\\n - [Exotel](/docs/integrations/exotel)\\n - [Slack](/docs/integrations/slack)\\n - [WhatsApp](/docs/integrations/whatsapp)\\n - [GitHub](/docs/integrations/github)\\n - [GitLab](/docs/integrations/gitlab)\\n - [Harness](/docs/integrations/harness)\\n - [Marker.io](/docs/integrations/marker-io)\\n - [Instabug](/docs/integrations/instabug)\\n - [Qase](/docs/integrations/qase)\\n - [Tracxn", - "title": "Account and contact import | Computer for Growth Teams | DevRev" + "id": "ART-1960_KNOWLEDGE_NODE-26", + "text": "address.\\n: Terms related to\\xc2\\xa0*account*:\\n\\n * *[customer](#customer)*\\n * *[workspace](#workspace)*\\n: Read more about\\xc2\\xa0[*account*](https://docs.devrev.ai/product/grow)\\n\\ncapability\\n\\n: A collection of features that enable a customer to achieve a use case.\\n: Capability is a unit of licensing and entitlement for the persona driving a particular use case. As a collection of features, capabilities are grouped into different buckets for tiered use cases (for example,", + "title": "Glossary | Computer by DevRev | DevRev" }, { - "id": "ART-2032_KNOWLEDGE_NODE-28", - "text": "Emails**: Events containing any of these email addresses are completely excluded from sync. No meetings are created in DevRev for events where these emails appear as attendees, organizers, or creators. Enter multiple emails separated by commas.\\n * **Add non-existing customers**: Enable this to allow people in meeting that are not customer to be added as a customer.\\n\\nIf a meeting is scheduled with people who are neither part of the company nor customers, this option allows them to be added", - "title": "Google Calendar | Integrate | Snap-ins | DevRev" + "id": "ART-15506_KNOWLEDGE_NODE-6", + "text": "[here](https://devrev.ai/docs/product/grow).\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl --location \\'https://api.devrev.ai/auth-tokens.create\\' \\\\ |\\n| > | --header \\'accept: application/json, text/plain, */*\\' \\\\ |\\n| > | --header \\'authorization: \\' \\\\ |\\n| > | --header \\'content-type: application/json\\' \\\\ |\\n| > | --data-raw \\'{ |\\n| > | \"rev_info\": { |\\n| > | \"user_ref\": \"example@devrev.ai\", |\\n| > | \"account_ref\": \"devrev.ai\", |\\n| > | \"workspace_ref\": \"devrev-dev\", |\\n| > |", + "title": "Identify your users with Plug | DevRev | Docs" }, { - "id": "ART-2002_KNOWLEDGE_NODE-26", - "text": "(for example Stripe as a customer of Slack) or a workspace in your software product (such as a Slack workspace).\\n\\nCreate a new customer contact\\n-----------------------------\\n\\n1. Go to **Contacts** > **+ Contact**.\\n2. Fill in the following fields as **Add Display Name, Description, Domains, Tags, Tiers**.\\n3. Click **Create**.\\n\\nWhile creating new customer records, be sure to specify the [**External Reference**](#external-reference) so customer information coming from other channels (like", - "title": "Contacts | Computer for Growth Teams | DevRev" + "id": "ART-6175_KNOWLEDGE_NODE-26", + "text": "contacts.\\n* **Link Account and Contact:**\\n Enable this option to link the account and contact to the custom object.\\n* **Account Description Fields:**\\n Enable this option to generate a rich description for accounts using values from multiple Airtable columns.\\n* **Contact Description Fields:**\\n Enable this option to generate a rich description for contacts using values from multiple Airtable columns.\\n* **Airtable Email Columns:**\\n Comma-separated list of names of the columns in", + "title": "Airtable | Automate | Snap-ins | DevRev" }, { - "id": "ART-1953_KNOWLEDGE_NODE-8", - "text": "tracking](/docs/plug/cross-domain-session)\\n + [Nudges](/docs/plug/nudges)\\n* [Computer for Growth Teams](/docs/product/grow)\\n\\n + [Accounts](/docs/product/account)\\n + [Opportunities](/docs/product/opportunity)\\n + [Contacts](/docs/product/customers)\\n + [Account and contact import](/docs/product/account-contact-import)\\n + [Grow snap-ins](/docs/product/snapins-grow)\\n* [Snap-ins](/docs/snapins)\\n\\n + [Automate](/docs/automate)\\n\\n - [Account", - "title": "Customer email notifications | Computer by DevRev | DevRev" + "id": "ART-1458_KNOWLEDGE_NODE-1", + "text": "[Accounts](https://docs.devrev.ai/product/grow#-account).\\n\\nWas this page helpful?YesNo\\n\\n[Create AccountUp Next](/public/api-reference/accounts/create)\\n\\n[Built with](https://buildwithfern.com/?utm_campaign=buildWith&utm_medium=docs&utm_source=developer.devrev.ai)\\n\\n[Enterprise grade security to protect customer dataLearn more about it.](https://devrev.ai/blog/soc-compliance)\\n\\nProduct\\n\\n * [Build](https://devrev.ai/build)\\n * [Support](https://devrev.ai/support)\\n *", + "title": "Accounts \u2014 DevRev | Docs" } ] }, @@ -2468,54 +2468,54 @@ "query": "list agents API for account", "retrievals": [ { - "id": "ART-1465_KNOWLEDGE_NODE-17", - "text": "Agents?](https://devrev.ai/what-are-ai-agents)\\n * [What is Agentic AI?](https://devrev.ai/what-is-agentic-ai)\\n * [What is Enterprise Search?](https://devrev.ai/what-is-enterprise-search)\\n * [What is Conversational AI?](https://devrev.ai/what-is-conversational-ai)\\n\\n[](https://devrev.ai)\\n\\n[](https://www.linkedin.com/company/devrev)[](https://medium.com/devrev)[](https://twitter.com/devrev)\\n\\n[System Status](https://devrev.ai/status)\\n\\n\\xc2\\xa9 2025 DevRev Inc.\\n\\n'", - "title": "List Accounts (POST) \u2014 DevRev | Docs" - }, - { - "id": "ART-1464_KNOWLEDGE_NODE-13", - "text": "Agents?](https://devrev.ai/what-are-ai-agents)\\n * [What is Agentic AI?](https://devrev.ai/what-is-agentic-ai)\\n * [What is Enterprise Search?](https://devrev.ai/what-is-enterprise-search)\\n * [What is Conversational AI?](https://devrev.ai/what-is-conversational-ai)\\n\\n[](https://devrev.ai)\\n\\n[](https://www.linkedin.com/company/devrev)[](https://medium.com/devrev)[](https://twitter.com/devrev)\\n\\n[System Status](https://devrev.ai/status)\\n\\n\\xc2\\xa9 2025 DevRev Inc.\\n\\n'", - "title": "Get Account (POST) \u2014 DevRev | Docs" + "id": "ART-1258_KNOWLEDGE_NODE-0", + "text": "b'List Accounts | DevRev | Docs\\n\\n[![]()![]()](https://developer.devrev.ai/)\\n\\nPublic\\n\\nPublic\\n\\nSearch\\n\\n`/`\\n\\n[API Reference](/api-reference/getting-started)[accounts](/api-reference/accounts/accounts)\\n\\nList Accounts\\n=============\\n\\nCopy page\\n\\nGET\\n\\nhttps://api.devrev.ai/accounts.list\\n\\nGET\\n\\n/accounts.list\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl https://api.devrev.ai/accounts.list \\\\ |\\n| > | -H \"Authorization: Bearer \" |\\n```\\n\\n[Try", + "title": "List Accounts | DevRev | Docs" }, { - "id": "ART-1465_KNOWLEDGE_NODE-1", - "text": "__\\n\\n[Pricing](https://devrev.ai/pricing)\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](https://devrev.ai/request-a-demo)\\n\\n[API Reference](/public/api-reference/getting-started)[Accounts](/public/api-reference/accounts/accounts)\\n\\n# List Accounts (POST)\\n\\nPOST\\n\\nhttps://api.devrev.ai/accounts.list\\n\\nTry it\\n\\nGets a list of accounts.\\n\\n### Request\\n\\nThis endpoint expects an object.\\n\\ncreated_bylist of stringsOptional\\n\\nFilters for accounts created by the specified", - "title": "List Accounts (POST) \u2014 DevRev | Docs" + "id": "ART-1306_KNOWLEDGE_NODE-19", + "text": "api.devrev.ai / accounts.list\\nGets a list of accounts.\\nRequest.\\n\\nThis endpoint expects an object.\\ncreated_by list of strings Optional\\nFilters for accounts created by the specified user(s).\\ncreated_date object Optional\\nShow 2 properties\\ncursor string Optional\\nThe cursor to resume iteration from. If not provided, then iteration starts from the beginning.\\ncustom_fields map from strings to any Optional\\nFilters for custom fields.\\ndisplay_name list of strings Optional\\nArray of display", + "title": "List \u2014 DevRev | Docs" }, { - "id": "ART-1257_KNOWLEDGE_NODE-6", - "text": "Response\\n\\nThe returned account.\\n\\naccountobject\\n\\nShow 14 properties\\n\\n### Errors\\n\\n400\\n\\nBad Request Error\\n\\n401\\n\\nUnauthorized Error\\n\\n403\\n\\nForbidden Error\\n\\n404\\n\\nNot Found Error\\n\\n429\\n\\nToo Many Requests Error\\n\\n500\\n\\nInternal Server Error\\n\\n503\\n\\nService Unavailable Error\\n\\nWas this page helpful?\\n\\nYesNo\\n\\n[Previous](/api-reference/accounts/get)[#### List Accounts\\n\\nNext](/api-reference/accounts/list)[Built", - "title": "Get Account (POST) | DevRev | Docs" + "id": "ART-1305_KNOWLEDGE_NODE-21", + "text": "api.devrev.ai / accounts.list\\nGets a list of accounts.\\nRequest.\\n\\nThis endpoint expects an object.\\ncreated_by list of strings Optional\\nFilters for accounts created by the specified user(s).\\ncreated_date object Optional\\nShow 2 properties\\ncursor string Optional\\nThe cursor to resume iteration from. If not provided, then iteration starts from the beginning.\\ncustom_fields map from strings to any Optional\\nFilters for custom fields.\\ndisplay_name list of strings Optional\\nArray of display", + "title": "Get Post \u2014 DevRev | Docs" }, { - "id": "ART-1453_KNOWLEDGE_NODE-1", - "text": "__\\n\\n[Pricing](https://devrev.ai/pricing)\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](https://devrev.ai/request-a-demo)\\n\\n[API Reference](/public/api-reference/getting-started)[Accounts](/public/api-reference/accounts/accounts)\\n\\n# List Accounts\\n\\nGET\\n\\nhttps://api.devrev.ai/accounts.list\\n\\nTry it\\n\\nGets a list of accounts.\\n\\n### Query parameters\\n\\ncreated_bylist of stringsOptional\\n\\nFilters for accounts created by the specified", - "title": "List Accounts \u2014 DevRev | Docs" + "id": "ART-1302_KNOWLEDGE_NODE-17", + "text": "of the account to be retrieved.\\nResponse.\\n\\nThis endpoint returns an object.\\naccount object\\nShow 18 properties\\nAPI Reference accounts List.\\n\\nGET https:// api.devrev.ai / accounts.list\\nGets a list of accounts.\\nQuery parameters.\\n\\ncreated_by string Optional\\nFilters for accounts created by the specified user(s).\\ncreated_date.after datetime Optional\\nFilters for objects created after the provided timestamp (inclusive).\\ncreated_date.before datetime Optional\\nFilters for objects created", + "title": "Export \u2014 DevRev | Docs" }, { - "id": "ART-1564_KNOWLEDGE_NODE-9", - "text": "objects\\n\\nThe exported accounts.\\n\\nShow 18 properties\\nAPI Reference accounts Get.\\n\\nGET https://api.devrev.ai / accounts.get\\n\\nRetrieves an account\\xe2\\x80\\x99s information.\\n\\nQuery parameters.\\n\\nid string Required\\n\\nThe ID of the account to be retrieved.\\n\\nResponse.\\n\\nThis endpoint returns an object.\\naccount object\\nShow 18 properties\\nAPI Reference accounts Get Post.\\n\\nPOST https://api.devrev.ai / accounts.get\\n\\nRetrieves an account\\xe2\\x80\\x99s information.\\n\\nRequest.\\n\\nThis", - "title": "List (Beta) \u2014 DevRev | Docs" + "id": "ART-1301_KNOWLEDGE_NODE-17", + "text": "of the account to be retrieved.\\nResponse.\\n\\nThis endpoint returns an object.\\naccount object\\nShow 18 properties\\nAPI Reference accounts List.\\n\\nGET https:// api.devrev.ai / accounts.list\\nGets a list of accounts.\\nQuery parameters.\\n\\ncreated_by string Optional\\nFilters for accounts created by the specified user(s).\\ncreated_date.after datetime Optional\\nFilters for objects created after the provided timestamp (inclusive).\\ncreated_date.before datetime Optional\\nFilters for objects created", + "title": "Delete \u2014 DevRev | Docs" }, { "id": "ART-1259_KNOWLEDGE_NODE-0", - "text": "b'List Accounts (POST) | DevRev | Docs\\n\\n[![]()![]()](https://developer.devrev.ai/)\\n\\nPublic\\n\\nPublic\\n\\nSearch\\n\\n`/`\\n\\n[API Reference](/api-reference/getting-started)[accounts](/api-reference/accounts/accounts)\\n\\nList Accounts (POST)\\n====================\\n\\nCopy page\\n\\nPOST\\n\\nhttps://api.devrev.ai/accounts.list\\n\\nPOST\\n\\n/accounts.list\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl -X POST https://api.devrev.ai/accounts.list \\\\ |\\n| > | -H \"Authorization: Bearer \" \\\\ |\\n| > | -H", + "text": "b'List Accounts (POST) | DevRev | Docs\\n\\n[![]()![]()](https://developer.devrev.ai/)\\n\\nPublic\\n\\nPublic\\n\\nSearch\\n\\n`/`\\n\\n[API Reference](/api-reference/getting-started)[accounts](/api-reference/accounts/accounts)\\n\\nList Accounts (POST)\\n====================\\n\\nCopy page\\n\\nPOST\\n\\nhttps://api.devrev.ai/accounts.list\\n\\nPOST\\n\\n/accounts.list\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl -X POST https://api.devrev.ai/accounts.list \\\\ |\\n| > | -H \"Authorization: Bearer \" \\\\ |\\n| > | -H", "title": "List Accounts (POST) | DevRev | Docs" }, { - "id": "ART-1259_KNOWLEDGE_NODE-9", - "text": "criteria.\\n\\naccountslist of objects\\n\\nList containing all the accounts\\n\\nShow 14 properties\\n\\nnext\\\\_cursorstring or null`format: \"text\"`\\n\\nThe cursor used to iterate subsequent results in accordance to the\\nsort order. If not set, then no later elements exist.\\n\\nprev\\\\_cursorstring or null`format: \"text\"`\\n\\nThe cursor used to iterate preceding results in accordance to the\\nsort order. If not set, then no prior elements exist.\\n\\n### Errors\\n\\n400\\n\\nBad Request", - "title": "List Accounts (POST) | DevRev | Docs" + "id": "ART-1300_KNOWLEDGE_NODE-14", + "text": "endpoint returns an object.\\naccount object\\nShow 18 properties\\nAPI Reference accounts List.\\n\\nGET https:// api.devrev.ai / accounts.list\\nGets a list of accounts.\\nQuery parameters.\\n\\ncreated_by string Optional\\nFilters for accounts created by the specified user(s).\\ncreated_date.after datetime Optional\\nFilters for objects created after the provided timestamp (inclusive).\\ncreated_date.before datetime Optional\\nFilters for objects created before the provided timestamp (inclusive).\\ncursor", + "title": "Create \u2014 DevRev | Docs" }, { - "id": "ART-1590_KNOWLEDGE_NODE-9", - "text": "object.\\naccount object\\nShow 18 properties\\nAPI Reference accounts Get Post.\\n\\nPOST https:// api.devrev.ai / accounts.get\\nRetrieves an account\\'s information.\\nRequest.\\n\\nThis endpoint expects an object.\\nid string Required\\nThe ID of the account to be retrieved.\\nResponse.\\n\\nThis endpoint returns an object.\\naccount object\\nShow 18 properties\\nAPI Reference accounts List.\\n\\nGET https:// api.devrev.ai / accounts.list\\nGets a list of accounts.\\nQuery parameters.\\n\\ncreated_by string", - "title": "List \u2014 DevRev | Docs" + "id": "ART-1305_KNOWLEDGE_NODE-14", + "text": ", 37 \" tier \" : \" tier \" 38 } 39 }\\nAPI Reference accounts List.\\n\\nGET https:// api.devrev.ai / accounts.list\\nGets a list of accounts.\\nQuery parameters.\\n\\ncreated_by string Optional\\nFilters for accounts created by the specified user(s).\\ncreated_date.after datetime Optional\\nFilters for objects created after the provided timestamp (inclusive).\\ncreated_date.before datetime Optional\\nFilters for objects created before the provided timestamp (inclusive).\\ncursor string Optional\\nThe cursor", + "title": "Get Post \u2014 DevRev | Docs" }, { - "id": "ART-1595_KNOWLEDGE_NODE-9", - "text": "object.\\naccount object\\nShow 18 properties\\nAPI Reference accounts Get Post.\\n\\nPOST https:// api.devrev.ai / accounts.get\\nRetrieves an account\\'s information.\\nRequest.\\n\\nThis endpoint expects an object.\\nid string Required\\nThe ID of the account to be retrieved.\\nResponse.\\n\\nThis endpoint returns an object.\\naccount object\\nShow 18 properties\\nAPI Reference accounts List.\\n\\nGET https:// api.devrev.ai / accounts.list\\nGets a list of accounts.\\nQuery parameters.\\n\\ncreated_by string", - "title": "List \u2014 DevRev | Docs" + "id": "ART-1453_KNOWLEDGE_NODE-0", + "text": "b'[](/public/api-reference/accounts/list)\\n\\nPublic\\n\\n[](https://devrev.ai)\\n\\n * Product\\n * Platform\\n * Solutions\\n * Marketplace\\n * Company\\n * Resources\\n * [Pricing](https://devrev.ai/pricing)\\n\\n __\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](https://devrev.ai/request-a-demo)\\n\\n[](https://devrev.ai)\\n\\n __\\n\\nProduct __\\n\\nPlatform __\\n\\nSolutions __\\n\\nMarketplace __\\n\\nCompany __\\n\\nResources", + "title": "List Accounts \u2014 DevRev | Docs" + }, + { + "id": "ART-2933_KNOWLEDGE_NODE-22", + "text": "created in **Accounts** and selecting the **Contacts** tab to view all the contacts created for the selected account.\\n\\n![]()\\n\\nWas this page helpful?\\n\\nYesNo\\n\\n[Previous](/beta/changelog/2024/12/2)[#### Agents async API\\n\\nNext](/beta/guides/agents-async-api)[Built with](https://buildwithfern.com/?utm_campaign=buildWith&utm_medium=docs&utm_source=developer.devrev.ai)\\n\\n![]()'", + "title": "Account creation | DevRev | Docs" } ] }, @@ -2524,54 +2524,54 @@ "query": "SLA timer not running for newly created tickets with L1 SLA tag and Test SLA Pilot", "retrievals": [ { - "id": "ART-1986_KNOWLEDGE_NODE-45", - "text": "selected on the ticket is not assigned any SLA.\\n\\n\\xc2\\xa0\\xc2\\xa0 \\xc2\\xa0 - Action: Check your SLA assignment rules or add the customer as an exception to any of your SLAs.\\n\\n![]()\\n\\nThe **SLA Name** is never empty if your organization has a default SLA.\\n\\n1. Verify policy conditions:\\n\\n\\xc2\\xa0\\xc2\\xa0 - If the **SLA Name** is populated but you still see no SLA metrics running on the ticket, the ticket does not satisfy the conditions of any policy within the SLA.\\n\\n\\xc2\\xa0\\xc2\\xa0", - "title": "Service-level agreement | Computer for Support Teams | DevRev" + "id": "ART-6174_KNOWLEDGE_NODE-32", + "text": "handling**: Conversation and ticket SLAs operate independently. When converting:\\n\\n + The new ticket starts with its own response and resolution SLA timers\\n + All active SLA metrics on the original conversation are marked as completed\\n\\n[PreviousConversations](/docs/product/conversation)[NextTickets](/docs/product/tickets)\\n\\n#### On this page\\n\\n* [Conversation conversion process](#conversation-conversion-process)\\n* [Convert conversations to tickets](#convert-conversations-to-tickets)\\n*", + "title": "Conversation to ticket conversion | Conversations | Computer for Support Teams | DevRev" }, { - "id": "ART-1986_KNOWLEDGE_NODE-44", - "text": "**Custom**: Filters all tickets that will breach by the selected date.\\n\\n![]()\\n\\nTroubleshooting: No SLA running on the ticket\\n---------------------------------------------\\n\\n### Issue\\n\\nYou have created and published an SLA, but no SLA is running on the ticket.\\n\\n### Solution\\n\\n1. Check the **SLA Name** attribute:\\n\\n\\xc2\\xa0\\xc2\\xa0 - Verify that the **SLA Name** attribute on the ticket is not empty.\\n\\n\\xc2\\xa0\\xc2\\xa0 - If the **SLA Name** is empty, it means the customer account", + "id": "ART-1986_KNOWLEDGE_NODE-41", + "text": "resolution is due in one day, the vista displays five minutes. In the case where the first response isn't provided within five minutes, the timer displays negative values (such as -10m), which indicates that it's been 10 minutes since the first response was due. Conversations or tickets can also be grouped by SLA stages.\\n\\nIn the **Detailed View**, all metrics applied to the ticket or conversation can be viewed along with their current stage.\\n\\nFiltering tickets by Next SLA", "title": "Service-level agreement | Computer for Support Teams | DevRev" }, { - "id": "ART-2017_KNOWLEDGE_NODE-28", - "text": "you would like to tag on the message (the ticket owner gets tagged automatically); and the target Slack channel. The channel\\'s ID can be found by going to the channel details. Refer to the placeholder value on the input to see an example of how this looks.\\n2. Decide if notifications should go out even if the ticket has a target end date set. Set the toggle to the desired behavior.\\n3. Decide if a ticket should pass the check if it\\'s part is a descendant of the filter part. For example, if a", - "title": "SLA status change Slack notifier | Automate | Snap-ins | DevRev" + "id": "ART-4181_KNOWLEDGE_NODE-18", + "text": "breach\\n\\n![]()\\n\\nSLA timers on Conversation and Ticket panel\\n\\nEquip agents with the comprehensive context they need to prioritize based on service level commitments\\n\\n![]()\\n\\nSLA timers on Conversation and Ticket panel\\n\\nEquip agents with the comprehensive context they need to prioritize based on service level commitments\\n\\n![]()\\n\\nView SLA targets in Inbox view\\n\\nSee critical SLA information directly on your Omnichannel Inbox to prioritize and take action before breach", + "title": "Support like a lightning fast pit-crew" }, { - "id": "ART-1986_KNOWLEDGE_NODE-35", - "text": "of schedule when they remain at the same stage, but time spent out of schedule isn't included in the calculation.\\n\\n![]()\\n\\nIf the customer account is updated after the ticket is created, all SLA metrics will be recalculated based on the updated customer account information. Any previous SLA breaches or achievements will be discarded, and new calculations will be applied according to the updated SLA.\\n\\nThe following table describes how each metric works for tickets and", - "title": "Service-level agreement | Computer for Support Teams | DevRev" + "id": "ART-1275_KNOWLEDGE_NODE-19", + "text": "owned_by: [\"DEVU-1\"], |\\n| 23 | type: publicSDK.WorkType.Ticket, |\\n| 24 | }); |\\n| 25 | |\\n| 26 | console.log(response); |\\n| 27 | } |\\n| 28 | }; |\\n| 29 | |\\n| 30 | export default run; |\\n```\\n\\n[6](/snapin-development/tutorials/timer-ticket-creator#deploying-the-snap-in-to-your-organization)\\n\\n### Deploying the snap-in to your organization\\n\\nOnce satisfied with the code changes, move to the `code` folder, and run\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | npm install |\\n| > | |\\n| > | npm", + "title": "Using a snap-in to perform a DevRev action | DevRev | Docs" }, { - "id": "ART-15281_KNOWLEDGE_NODE-2", - "text": "| \"completed_in\": 1, |\\n| 16 | \"in_policy\": true, |\\n| 17 | \"is_out_of_schedule\": true, |\\n| 18 | \"next_schedule_transition\": \"2023-01-01T12:00:00.000Z\", |\\n| 19 | \"org_schedule\": { |\\n| 20 | \"id\": \"string\", |\\n| 21 | \"status\": \"archived\", |\\n| 22 | \"display_id\": \"string\", |\\n| 23 | \"name\": \"string\", |\\n| 24 | \"timezone\": \"string\", |\\n| 25 | \"valid_until\": \"2023-01-01T12:00:00.000Z\" |\\n| 26 | }, |\\n| 27 | \"remaining_time\": 1, |\\n| 28 | \"status\": \"string\", |\\n| 29 | \"target_time\":", - "title": "List SLA Trackers | DevRev | Docs" + "id": "ART-2017_KNOWLEDGE_NODE-25", + "text": "ticket\\'s owner and subscribers, when a ticket\\'s resolution time SLA changes into the *Warning* or *Breached* stage.\\n\\n![]()\\n\\nFor more information, refer to the\\n[SLA status change Slack notifier snap-in](/marketplace/sla-status-change-slack-notifier) on the DevRev\\nmarketplace.\\n\\nInstallation\\n------------\\n\\n1. Create a Slack app for your workspace in .\\n2. In App features, generate bot token in **OAuth & Permissions**.\\n3. Grant the app bot the following", + "title": "SLA status change Slack notifier | Automate | Snap-ins | DevRev" }, { - "id": "ART-1262_KNOWLEDGE_NODE-2", - "text": "| \"completed_in\": 1, |\\n| 15 | \"in_policy\": true, |\\n| 16 | \"is_out_of_schedule\": true, |\\n| 17 | \"next_schedule_transition\": \"2023-01-01T12:00:00.000Z\", |\\n| 18 | \"org_schedule\": { |\\n| 19 | \"id\": \"string\", |\\n| 20 | \"status\": \"archived\", |\\n| 21 | \"display_id\": \"string\", |\\n| 22 | \"name\": \"string\", |\\n| 23 | \"timezone\": \"string\", |\\n| 24 | \"valid_until\": \"2023-01-01T12:00:00.000Z\" |\\n| 25 | }, |\\n| 26 | \"remaining_time\": 1, |\\n| 27 | \"status\": \"string\", |\\n| 28 | \"target_time\":", - "title": "Get SLA Tracker | DevRev | Docs" + "id": "ART-1273_KNOWLEDGE_NODE-1", + "text": "action](/snapin-development/tutorials/timer-ticket-creator)\\n3. [Snap-in triggered by a DevRev event](/snapin-development/tutorials/triggered-event)\\n4. [Snap-in triggered by an external source](/snapin-development/tutorials/triggered-external-source)\\n5. [Using snap-in to perform an external action](/snapin-development/tutorials/perform-external-action)\\n\\nWas this page helpful?\\n\\nYesNo\\n\\n[Previous](/snapin-development/concepts)[#### Getting", + "title": "Overview | DevRev | Docs" }, { - "id": "ART-1986_KNOWLEDGE_NODE-28", - "text": "*Conversation Policy*.\\n3. In the **New ticket policy** pane, under **Conditions**, select the ticket attributes values of **Tag**, **Part**, and **Severity**.\\n4. Under **Metrics**, enable or disable **First response**, **Next response**, and **Resolution time**.\\n5. Click **Publish**.\\n\\n![]()\\n\\nSLA metrics are only applied to tickets or conversations that meet the policy's conditions.\\n\\nPublishing an SLA\\n-----------------\\n\\nSLAs can be published once all policies are created. Published", - "title": "Service-level agreement | Computer for Support Teams | DevRev" + "id": "ART-1275_KNOWLEDGE_NODE-7", + "text": "account\\xe2\\x80\\x99s display name to better reflect the\\nsnap-in\\xe2\\x80\\x99s behavior.\\n\\nmanifest.yaml\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | version: \"2\" |\\n| 2 | |\\n| 3 | name: \"Timely Ticketer\" |\\n| 4 | description: \"Snap-in to create ticket every 10 minutes\" |\\n| 5 | |\\n| 6 | service_account: |\\n| 7 | display_name: Automatic Ticket Creator Bot |\\n```\\n\\nNext, update the `event_sources` section to use the `timer-events` event source.\\nThe `timer-events` source type takes a `config` of", + "title": "Using a snap-in to perform a DevRev action | DevRev | Docs" }, { - "id": "ART-2632_KNOWLEDGE_NODE-7", - "text": "\"2023-01-01T12:00:00.000Z\", \\n 15| \"completed_in\": 42, \\n 16| \"in_policy\": true, \\n 17| \"is_out_of_schedule\": true, \\n 18| \"next_schedule_transition\": \"2023-01-01T12:00:00.000Z\", \\n 19| \"org_schedule\": { \\n 20| \"id\": \"foo\", \\n 21| \"status\": \"archived\", \\n 22| \"display_id\": \"foo\", \\n 23| \"name\": \"foo\", \\n 24| \"timezone\": \"foo\", \\n 25|", - "title": "List SLA Trackers (POST) \u2014 DevRev | Docs" + "id": "ART-1483_KNOWLEDGE_NODE-22", + "text": "27| } \\n 28| }; \\n 29| \\n 30| export default run;\\n[/code] \\n \\n[6](/public/snapin-development/tutorials/timer-ticket-creator#deploying-the-snap-in-to-your-organization)\\n\\n### Deploying the snap-in to your organization\\n\\nOnce satisfied with the code changes, move to the `code` folder, and run\\n\\n[code]\\n\\n $| npm install \\n ---|--- \\n >| \\n >| npm run build \\n >| \\n >| npm run package\\n[/code] \\n \\nThis builds and packages your snap-in and creates a", + "title": "Using a snap-in to perform a DevRev action \u2014 DevRev | Docs" }, { - "id": "ART-2017_KNOWLEDGE_NODE-25", - "text": "ticket\\'s owner and subscribers, when a ticket\\'s resolution time SLA changes into the *Warning* or *Breached* stage.\\n\\n![]()\\n\\nFor more information, refer to the\\n[SLA status change Slack notifier snap-in](/marketplace/sla-status-change-slack-notifier) on the DevRev\\nmarketplace.\\n\\nInstallation\\n------------\\n\\n1. Create a Slack app for your workspace in .\\n2. In App features, generate bot token in **OAuth & Permissions**.\\n3. Grant the app bot the following", - "title": "SLA status change Slack notifier | Automate | Snap-ins | DevRev" + "id": "ART-2043_KNOWLEDGE_NODE-13", + "text": "group](/docs/automations/set-user-preference)\\n - [SLA status change Slack notifier](/docs/automations/sla-change-notifier)\\n - [Slash commands](/docs/automations/slash-commands)\\n - [Spam Shield](/docs/automations/spam-shield)\\n - [Subtype Migration](/docs/automations/subtype-migration)\\n - [Ticket age in engineering](/docs/automations/ticket-age-in-engineering)\\n - [Ticket issue field migrator](/docs/automations/ticket-issue-field-migrator)\\n - [Ticket", + "title": "Glean | Integrate | Snap-ins | DevRev" }, { - "id": "ART-15280_KNOWLEDGE_NODE-2", - "text": "| \"breached_at\": \"2023-01-01T12:00:00.000Z\", |\\n| 14 | \"completed_at\": \"2023-01-01T12:00:00.000Z\", |\\n| 15 | \"completed_in\": 1, |\\n| 16 | \"in_policy\": true, |\\n| 17 | \"is_out_of_schedule\": true, |\\n| 18 | \"next_schedule_transition\": \"2023-01-01T12:00:00.000Z\", |\\n| 19 | \"org_schedule\": { |\\n| 20 | \"id\": \"string\", |\\n| 21 | \"status\": \"archived\", |\\n| 22 | \"display_id\": \"string\", |\\n| 23 | \"name\": \"string\", |\\n| 24 | \"timezone\": \"string\", |\\n| 25 | \"valid_until\": \"2023-01-01T12:00:00.000Z\" |\\n|", - "title": "List SLA Trackers (POST) | DevRev | Docs" + "id": "ART-15691_KNOWLEDGE_NODE-13", + "text": "group](/docs/automations/set-user-preference)\\n - [SLA status change Slack notifier](/docs/automations/sla-change-notifier)\\n - [Slash commands](/docs/automations/slash-commands)\\n - [Spam Shield](/docs/automations/spam-shield)\\n - [Subtype Migration](/docs/automations/subtype-migration)\\n - [Ticket age in engineering](/docs/automations/ticket-age-in-engineering)\\n - [Ticket issue field migrator](/docs/automations/ticket-issue-field-migrator)\\n - [Ticket", + "title": "May 2025 | Changelog | DevRev" } ] }, @@ -2580,9 +2580,9 @@ "query": "how to find secondary ticket", "retrievals": [ { - "id": "ART-1979_KNOWLEDGE_NODE-54", - "text": "already raised in the primary ticket. Duplicate tickets often arise from customers submitting multiple requests through different channels (email, portal, Slack). All duplicate tickets become *immutable* after merging.\\n\\n**Primary ticket**\\n\\nA primary ticket is the main record that consolidates all relevant information from duplicate tickets. It serves as the primary source of communication for all merged duplicate tickets, ensuring that all customer interactions, updates, and resolutions are", - "title": "Tickets | Computer for Support Teams | DevRev" + "id": "ART-15376_KNOWLEDGE_NODE-2", + "text": "tickets, parts\\netc. owned by the secondary Dev user will be transferred to the primary\\nDev user.\\n\\n### Headers\\n\\nAuthorizationstringRequired\\n\\nBearer authentication of the form `Bearer `, where token is your auth token.\\n\\n### Request\\n\\nThis endpoint expects an object.\\n\\nprimary\\\\_userstringRequired`format: \"id\"`\\n\\nThe unique ID of the primary user.\\n\\nsecondary\\\\_userstringRequired`format: \"id\"`\\n\\nThe unique ID of the secondary user.\\n\\n### Response\\n\\nResponse object for", + "title": "Merge Dev Users | DevRev | Docs" }, { "id": "ART-1979_KNOWLEDGE_NODE-59", @@ -2590,44 +2590,44 @@ "title": "Tickets | Computer for Support Teams | DevRev" }, { - "id": "ART-1979_KNOWLEDGE_NODE-57", - "text": "only when users configure the post merge stage in the ticket preference settings page.\\n\\n### Merge tickets\\n\\n1. Open the primary ticket and select the merge option from the side panel.\\n\\n ![]()\\n\\n The ticket from which you initiate the merge becomes the primary ticket.\\n2. In the modal window that appears, review the suggested duplicate tickets based on the pre-filled primary ticket title.\\n3. Select the appropriate duplicate tickets and confirm the merge action.\\n\\n There is no limit", - "title": "Tickets | Computer for Support Teams | DevRev" + "id": "ART-15664_KNOWLEDGE_NODE-6", + "text": "you want to establish a parent-child relationship between tickets and a custom object\\ntype called \\xe2\\x80\\x9cCampaign\\xe2\\x80\\x9d. This relationship helps track which tickets are assigned to which campaigns.\\n\\nTo create this relationship, make an API call to create a link type:\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl --location \\'https://api.devrev.ai/link-types.custom.create\\' \\\\ |\\n| > | --header \\'Content-Type: application/json\\' \\\\ |\\n| > | --header \\'Authorization: Bearer \\'", + "title": "Links | DevRev | Docs" }, { - "id": "ART-1979_KNOWLEDGE_NODE-58", - "text": "on the number of tickets that can be merged.\\n4. Review the automatic communication sent to primary and duplicate ticket owners (configurable in ticket preferences).\\n\\n### Post-merge conditions\\n\\n* The primary ticket retains all key fields (description, part, group, owner, creator, priority, stage), and the SLA remains unchanged.\\n* Events are updated to reflect all merge actions.\\n* Subscribers and reporters from duplicate tickets are added to the primary ticket.\\n* Linked objects from", + "id": "ART-1979_KNOWLEDGE_NODE-54", + "text": "already raised in the primary ticket. Duplicate tickets often arise from customers submitting multiple requests through different channels (email, portal, Slack). All duplicate tickets become *immutable* after merging.\\n\\n**Primary ticket**\\n\\nA primary ticket is the main record that consolidates all relevant information from duplicate tickets. It serves as the primary source of communication for all merged duplicate tickets, ensuring that all customer interactions, updates, and resolutions are", "title": "Tickets | Computer for Support Teams | DevRev" }, { - "id": "ART-1979_KNOWLEDGE_NODE-56", - "text": "reporters or no reporters.\\n* Active status: Only unclosed tickets can be selected as primary or duplicate tickets.\\n* Channel flexibility: Tickets from any channel can be merged if they share the same reporters.\\n\\n### Merge settings\\n\\nYou can configure the following options in the ticket preferences page:\\n\\n* Communication messages for duplicate and primary ticket owners\\n* Stage of duplicate tickets after merge\\n* Accounts to exclude from automated messages\\n\\n![]()\\n\\nMerge can be enabled", + "id": "ART-1979_KNOWLEDGE_NODE-58", + "text": "on the number of tickets that can be merged.\\n4. Review the automatic communication sent to primary and duplicate ticket owners (configurable in ticket preferences).\\n\\n### Post-merge conditions\\n\\n* The primary ticket retains all key fields (description, part, group, owner, creator, priority, stage), and the SLA remains unchanged.\\n* Events are updated to reflect all merge actions.\\n* Subscribers and reporters from duplicate tickets are added to the primary ticket.\\n* Linked objects from", "title": "Tickets | Computer for Support Teams | DevRev" }, { - "id": "ART-1979_KNOWLEDGE_NODE-39", - "text": "other tickets or issues that relate to this ticket, click **Link Records** and select the relevant items.\\n7. If you would like to immediately create another ticket, select **Create multiple**.\\n8. Click **Create**.\\n\\nIf a ticket is created from an existing conversation, then the ticket's title and description are populated automatically from the conversation.\\n\\n![]()\\n\\nYou can create a child issue by clicking **+ Link issue** > **Add a child issue**. You can link the other existing issue as", - "title": "Tickets | Computer for Support Teams | DevRev" + "id": "ART-15664_KNOWLEDGE_NODE-13", + "text": "\\n\\nYou may want to restrict links to specific subtypes of objects. For example, only allowing issues\\nof a particular subtype to be linked to tickets.\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl --location \\'https://api.devrev.ai/link-types.custom.create\\' \\\\ |\\n| > | --header \\'Content-Type: application/json\\' \\\\ |\\n| > | --header \\'Authorization: Bearer \\' \\\\ |\\n| > | --data \\'{ |\\n| > | \"name\": \"Link between social media issues and tickets\", |\\n| > | \"source_types\": [ |\\n| > | { |\\n|", + "title": "Links | DevRev | Docs" }, { - "id": "ART-1979_KNOWLEDGE_NODE-60", - "text": "tickets\\n-----------------\\n\\nFollow up tickets allow support teams to seamlessly address unresolved issues, recurring problems, or additional concerns without losing context. By linking follow-up tickets to the original ticket(archived/immutable), teams can track ongoing issues more effectively, minimize duplicate work and enhance customer experience. A follow-up ticket is a new ticket that is created and linked when a customer responds in reference to an archived/immutable ticket. The", - "title": "Tickets | Computer for Support Teams | DevRev" + "id": "ART-1483_KNOWLEDGE_NODE-18", + "text": "the code\\n\\nUpdate the code in `src/functions/ticket_creator/index.ts` to reflect the behavior.\\n\\nFirstly, import the DevRev TypeScript SDK in the `index.ts` file\\n\\nindex.ts\\n\\n[code]\\n\\n 1| import {client, publicSDK} from \"@devrev/typescript-sdk\"; \\n ---|---\\n[/code] \\n \\nNext, update the `run` function in the hello-world example. Since the ticket gets created frequently, set some creation time in the title and the body. The example uses the part as `PROD-1` and keeps the owner as", + "title": "Using a snap-in to perform a DevRev action \u2014 DevRev | Docs" }, { - "id": "ART-1979_KNOWLEDGE_NODE-52", - "text": "don\\xe2\\x80\\x99t forget to give \\xf0\\x9f\\x91\\x8d on the suggestion if you like it or \\xf0\\x9f\\x91\\x8e to dislike it.\\n\\n![]()\\n\\nDuplicate ticket merging\\n------------------------\\n\\nDuplicate tickets in a support system pose a significant challenge by creating inefficiencies, increasing the workload for support agents, and negatively impacting user experience. These tickets often result from user frustration or misunderstandings of the resolution process, leading to confusion and disrupting", - "title": "Tickets | Computer for Support Teams | DevRev" + "id": "ART-3107_KNOWLEDGE_NODE-24", + "text": "existing tickets](#triggering-tag-checks-for-existing-tickets)\\n\\n1. [Documentation](/docs)\\n3. [Snap-ins](/docs/snapins)\\n[Automate](/docs/automate)\\n[Ticket Tagger](/docs/automations/ticket-tagger)\\n\\nTicket tagger\\n=============\\n\\nThe **Ticket Tagger** is an automation tool designed to streamline ticket\\nmanagement. It automatically assigns appropriate tags to tickets based on the\\ntags of the contact or their account.\\n\\nKey features\\n------------\\n\\n* Automatically tags tickets created by", + "title": "Ticket Tagger | Automate | Snap-ins | DevRev" }, { - "id": "ART-1979_KNOWLEDGE_NODE-64", - "text": "internal tickets.\\n\\nTo create an internal ticket, click the **Create Ticket** button. At the bottom of the ticket creation panel, click the dropdown menu on **Create external ticket** and select **Create internal ticket**.\\n\\nYou can convert an internal ticket to an external ticket by clicking **Convert to External** within the **Customer Messages** tab. Once a ticket is converted to external, it cannot be reverted back to internal.\\n\\n[PreviousConversation to ticket", - "title": "Tickets | Computer for Support Teams | DevRev" + "id": "ART-1961_KNOWLEDGE_NODE-37", + "text": "\\n{{Ticket\\xc2\\xa0Created\\xc2\\xa0>\\xc2\\xa0Output\\xc2\\xa0>\\xc2\\xa0Reported\\xc2\\xa0By\\xc2\\xa0>\\xc2\\xa0Rev\\xc2\\xa0Org\\xc2\\xa0>\\xc2\\xa0Display\\xc2\\xa0Name}}.\\xe2\\x80\\x9d\\n\\n\\n\\nDelay\\n\\n\\n\\nDuration: 2 minutes\\n\\n\\n\\nIf-else\\n\\n\\n\\nAttribute:\\xc2\\xa0Ticket\\xc2\\xa0Created/Output\\xc2\\xa0>\\xc2\\xa0Applies\\xc2\\xa0to\\xc2\\xa0part\\xc2\\xa0>\\xc2\\xa0Display\\xc2\\xa0ID \\nOperator: Equals \\nOperand: CAPL-18\\n\\n\\n\\nTicket \\ncreated\\n\\n\\n\\nEnd\\n```\\n\\n[### Workflow action", + "title": "Workflows | Computer by DevRev | DevRev" }, { - "id": "ART-1979_KNOWLEDGE_NODE-61", - "text": "following scenarios can lead to the creation of follow up ticket:\\n\\n* Customers communicated on an archived/immutable ticket from any channel such as email.\\n* Customer communicated on a merged ticket and the primary ticket is also archived.\\n\\nAfter creation of a follow up ticket the customer messages will reflect only on the new followup ticket and the customer will continue to see response on the same thread in channels like email & slack. The user can continue responding on the new follow", - "title": "Tickets | Computer for Support Teams | DevRev" + "id": "ART-1986_KNOWLEDGE_NODE-43", + "text": "tickets that have been in breach for more than one hour.\\n + **Over a day**: Filters all tickets that have been in breach for more than one day.\\n + **Custom**: Filters all tickets that have been in breach from a given date.\\n* **Will breach in**:\\n\\n + **Any**: Filters all tickets that are currently not in breach.\\n + **Over an hour**: Filters all tickets that have less than 1 hour left for breach.\\n + **Over a day**: Filters all tickets that have less than 1 day left for breach.\\n +", + "title": "Service-level agreement | Computer for Support Teams | DevRev" } ] }, @@ -2636,38 +2636,38 @@ "query": "converting conversations to tickets issue customer channel acme", "retrievals": [ { - "id": "ART-4271_KNOWLEDGE_NODE-29", - "text": "end user.\\n\\n## Why you should convert a Conversation to a Ticket\\n\\nConsider converting a conversation to a ticket in these scenarios:\\n\\n * **Complex issues** : When a customer inquiry requires in-depth investigation that can't be resolved in a quick conversation.\\n * **Cross-team collaboration** : Issues requiring input from multiple departments or specialists.\\n * **Escalation needs** : When a conversation needs to be escalated to a higher support tier.\\n * **Feature requests** :", + "id": "ART-4271_KNOWLEDGE_NODE-26", + "text": "conversation metadata including: \\n * Source channel\\n * Customer account information\\n * External members added as **reported by** on the ticket\\n * An AI-generated ticket title and description based on customer messages.\\n\\n### How to convert Conversations to Tickets\\n\\n**Manual Conversion**\\n\\nTo manually convert a conversation to a ticket:\\n\\n 1. Open the conversation record pane view.\\n 2. Click **Convert to Ticket** to initiate the conversion.\\n\\n**Automated Conversion", "title": "Convert Conversations to Tickets | Conversations | Support | DevRev" }, { - "id": "ART-4271_KNOWLEDGE_NODE-26", - "text": "conversation metadata including: \\n * Source channel\\n * Customer account information\\n * External members added as **reported by** on the ticket\\n * An AI-generated ticket title and description based on customer messages.\\n\\n### How to convert Conversations to Tickets\\n\\n**Manual Conversion**\\n\\nTo manually convert a conversation to a ticket:\\n\\n 1. Open the conversation record pane view.\\n 2. Click **Convert to Ticket** to initiate the conversion.\\n\\n**Automated Conversion", - "title": "Convert Conversations to Tickets | Conversations | Support | DevRev" + "id": "ART-6174_KNOWLEDGE_NODE-27", + "text": "happens automatically:\\n\\n* The original conversation moves to *Archived* stage and cannot be reopened.\\n* A new ticket is created with:\\n + All internal discussions and customer messages copied from the conversation\\n + Equivalent metadata as the conversation, including source channel, customer account information, and external members added as **reported by** on the ticket\\n + An AI-generated ticket title and description based on customer messages\\n\\nConvert conversations to", + "title": "Conversation to ticket conversion | Conversations | Computer for Support Teams | DevRev" }, { - "id": "ART-4271_KNOWLEDGE_NODE-31", - "text": "AI-handled conversation reaches its capability limits and needs human expertise.\\n * **Extended troubleshooting** : Issues requiring multiple steps or follow-ups over time.\\n\\n## Key information\\n\\n * **Channel support** : Currently, the conversion feature is only available for PLuG and Slack conversations. Other channels still use the traditional **Link Ticket** functionality.\\n\\n * **CSAT surveys** : CSAT surveys are not sent when a conversation is converted to a ticket. Surveys are only", + "id": "ART-4271_KNOWLEDGE_NODE-29", + "text": "end user.\\n\\n## Why you should convert a Conversation to a Ticket\\n\\nConsider converting a conversation to a ticket in these scenarios:\\n\\n * **Complex issues** : When a customer inquiry requires in-depth investigation that can't be resolved in a quick conversation.\\n * **Cross-team collaboration** : Issues requiring input from multiple departments or specialists.\\n * **Escalation needs** : When a conversation needs to be escalated to a higher support tier.\\n * **Feature requests** :", "title": "Convert Conversations to Tickets | Conversations | Support | DevRev" }, { - "id": "ART-6174_KNOWLEDGE_NODE-32", - "text": "handling**: Conversation and ticket SLAs operate independently. When converting:\\n\\n + The new ticket starts with its own response and resolution SLA timers\\n + All active SLA metrics on the original conversation are marked as completed\\n\\n[PreviousConversations](/docs/product/conversation)[NextTickets](/docs/product/tickets)\\n\\n#### On this page\\n\\n* [Conversation conversion process](#conversation-conversion-process)\\n* [Convert conversations to tickets](#convert-conversations-to-tickets)\\n*", + "id": "ART-6174_KNOWLEDGE_NODE-25", + "text": "Teams](/docs/product/support)\\n[Conversations](/docs/product/conversation)\\n[Conversation to ticket conversion](/docs/product/conversation-ticket)\\n\\nConversation to ticket conversion\\n=================================\\n\\nYou can convert conversations from Plug and Slack directly into tickets. Previously, conversations were only linked to tickets. This update streamlines workflows and enhances the customer experience.\\n\\nFor conversations originating from Plug or Slack, the **Link to Ticket**", "title": "Conversation to ticket conversion | Conversations | Computer for Support Teams | DevRev" }, { - "id": "ART-6174_KNOWLEDGE_NODE-27", - "text": "happens automatically:\\n\\n* The original conversation moves to *Archived* stage and cannot be reopened.\\n* A new ticket is created with:\\n + All internal discussions and customer messages copied from the conversation\\n + Equivalent metadata as the conversation, including source channel, customer account information, and external members added as **reported by** on the ticket\\n + An AI-generated ticket title and description based on customer messages\\n\\nConvert conversations to", - "title": "Conversation to ticket conversion | Conversations | Computer for Support Teams | DevRev" + "id": "ART-2024_KNOWLEDGE_NODE-27", + "text": "help now... ask again in 5d\\n\\nSample response:\\n\\n> I am unable to assist you at the moment, however please reach out to me again in five days and I will be happy to help you.\\n\\n### Summarize\\n\\nUsing the summarize command, you can sum up the entire conversation. It applies to the following:\\n\\n* Conversation\\n* Tickets\\n* Issues\\n* Part\\n* Workspace\\n* Customer\\n* Account\\n\\nSample response:\\n\\n> **Summary:**\\n>\\n> * Rahul from DummyOrg is having difficulty installing the Plug Widget.\\n> *", + "title": "Slash commands | Automate | Snap-ins | DevRev" }, { - "id": "ART-6174_KNOWLEDGE_NODE-28", - "text": "tickets\\n--------------------------------\\n\\n**Manual conversion**\\n\\nGo to the conversation record pane and select **Convert to Ticket** to create a new ticket from the conversation.\\n\\n![]()\\n\\n**Automated conversion via workflows**\\n\\nSet up automated [workflows](./workflow-engine) to convert conversations to tickets based on specific triggers:\\n\\n* When a conversation meets defined criteria\\n* When the AI agent identifies an issue requiring escalation\\n* According to custom business", - "title": "Conversation to ticket conversion | Conversations | Computer for Support Teams | DevRev" + "id": "ART-4271_KNOWLEDGE_NODE-25", + "text": "is being replaced with a new **Convert to Ticket** feature. This change provides a more seamless transition from conversation to ticket management.\\n\\n## How Conversation conversion works\\n\\nWhen you convert a conversation to a ticket, the following happens automatically:\\n\\n * The original conversation is moved to _Archived_ stage and cannot be reopened.\\n * A new ticket is created with: \\n * All internal discussions and customer messages copied from the conversation.\\n * Preserved", + "title": "Convert Conversations to Tickets | Conversations | Support | DevRev" }, { - "id": "ART-6174_KNOWLEDGE_NODE-31", - "text": "Cross-team collaboration needs\\n* Escalation requirements\\n* Feature requests\\n* Bug reports\\n* SLA tracking requirements\\n* Documentation needs\\n* Resource allocation requirements\\n* AI capability limitations\\n* Extended troubleshooting needs\\n\\nSupport workflows\\n-----------------\\n\\n* **CSAT surveys**: CSAT surveys are not sent when a conversation is converted to a ticket. Surveys are only triggered when a conversation is resolved, not when it's archived through conversion.\\n* **SLA", + "id": "ART-6174_KNOWLEDGE_NODE-32", + "text": "handling**: Conversation and ticket SLAs operate independently. When converting:\\n\\n + The new ticket starts with its own response and resolution SLA timers\\n + All active SLA metrics on the original conversation are marked as completed\\n\\n[PreviousConversations](/docs/product/conversation)[NextTickets](/docs/product/tickets)\\n\\n#### On this page\\n\\n* [Conversation conversion process](#conversation-conversion-process)\\n* [Convert conversations to tickets](#convert-conversations-to-tickets)\\n*", "title": "Conversation to ticket conversion | Conversations | Computer for Support Teams | DevRev" }, { @@ -2676,13 +2676,13 @@ "title": "Conversation to ticket conversion | Conversations | Computer for Support Teams | DevRev" }, { - "id": "ART-6174_KNOWLEDGE_NODE-30", - "text": "there.\\n\\n![]()\\n\\nSlack end-user experience\\n-------------------------\\n\\nWhen a conversation is converted to a ticket in Slack:\\n\\n* Ticket information appears within the same thread.\\n* All subsequent messages sync with the newly created ticket.\\n* The transition is seamless for the end user.\\n\\nConversation conversion scenarios\\n---------------------------------\\n\\nConsider converting a conversation to a ticket in these scenarios:\\n\\n* Complex issues requiring in-depth investigation\\n*", + "id": "ART-6174_KNOWLEDGE_NODE-29", + "text": "rules\\n\\nWorkflows enable seamless handovers from automated conversations to your support teams when necessary.\\n\\nPlug widget end-user experience\\n-------------------------------\\n\\nWhen a conversation is converted to a ticket in the Plug widget:\\n\\n* The ticket number and basic details appear in the same conversation pane.\\n* Users can click **Details** to view complete ticket information.\\n* If the **Tickets** tab is enabled in Plug, users can track their ticket status", "title": "Conversation to ticket conversion | Conversations | Computer for Support Teams | DevRev" }, { - "id": "ART-4271_KNOWLEDGE_NODE-8", - "text": "* [Automatic customer reply](/docs/automations/auto-reply?)\\n * [Auto parts to conversation](/docs/automations/auto-parts?)\\n * [Automate opportunities](/docs/automations/opportunity?)\\n * [Bulk delete data](/docs/automations/bulk-delete?)\\n * [Bulk work item uploader](/docs/automations/bulk-upload?)\\n * [Commands surface expander](/docs/automations/commands-surface-expander?)\\n * [Convergence](/docs/automations/converge?)\\n * [Conversation", + "id": "ART-4271_KNOWLEDGE_NODE-32", + "text": "triggered when a conversation is resolved, not when it's archived through conversion.\\n\\n * **SLA handling** : Conversation and ticket SLAs operate independently. When converting:\\n\\n * The new ticket starts with its own response and resolution SLA timers.\\n * All active SLA metrics on the original conversation are marked as completed.\\n * **Conversion permanence** : Conversion cannot be undone. Once a conversation is converted to a ticket, this action is permanent and the conversation", "title": "Convert Conversations to Tickets | Conversations | Support | DevRev" } ] @@ -2692,54 +2692,54 @@ "query": "add subtype in conversation in DevRev", "retrievals": [ { - "id": "ART-5010_KNOWLEDGE_NODE-0", - "text": "b'Subtype Migration | Automate | Snap-ins | DevRev\\n\\n* Computer\\n* Resources\\n* [Our Customers](/case-study)\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](/request-a-demo)\\n\\nComputer\\n\\nResources\\n\\n[Our Customers](/case-study)\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](/request-a-demo)\\n\\nSearch\\n\\n`CTRL`\\xc2\\xa0+\\xc2\\xa0`K`\\n\\n* [Introduction](/docs)\\n* [Computer by DevRev](/docs/intro)\\n\\n + [Core concepts](/docs/product/core)\\n + [Apps](/docs/product/apps)\\n +", - "title": "Subtype Migration | Automate | Snap-ins | DevRev" + "id": "ART-1510_KNOWLEDGE_NODE-10", + "text": "\"don:core:dvrv-us-1:devo/example:custom_type_fragment/custom-type-fragment-id\", \\n 115| \"subtype\": \"subtype\", \\n 116| \"tags\": [ \\n 117| { \\n 118| \"tag\": { \\n 119| \"id\": \"id\", \\n 120| \"name\": \"name\" \\n 121| } \\n 122| } \\n 123| ], \\n 124| \"title\": \"title\" \\n 125| } \\n 126| }\\n[/code] \\n \\n[Get Conversation (POST)Up Next](/beta/api-reference/conversations/get-post)\\n\\n[Built", + "title": "Get Conversation (Beta) \u2014 DevRev | Docs" }, { - "id": "ART-17231_KNOWLEDGE_NODE-58", - "text": "top](/airsync/supported-object-types#summary)\\n\\nconversation\\n------------\\n\\n**Resource Type:** `conversation`\\n\\n**Capabilities:** Can Load, Can Subtype\\n\\n### Fields\\n\\n| Field | Type | Required | Description |\\n| --- | --- | --- | --- |\\n| `applies_to_part_ids` | reference (collection)\\xe2\\x86\\x92[#category:part] | | Details of the parts relevant to the conversation. |\\n| `broadcast_channels` | text (collection) | | Active channels for the conversation |\\n| `channels` | reference", - "title": "Supported DevRev object types | DevRev | Docs" + "id": "ART-1957_KNOWLEDGE_NODE-24", + "text": "subtype](#add-a-new-subtype)\\n\\n1. [Documentation](/docs)\\n3. [Computer by DevRev](/docs/intro)\\n[Object customization](/docs/product/object-customization)\\n\\nObject customization\\n====================\\n\\nDevRev powers your organization with the ability to customize DevRev objects for your organization\\'s needs. You can add custom fields to the objects along with the pre-existing fields or add new subtypes to the objects which helps you extend an object\\'s capabilities.\\nObjects are the core", + "title": "Object customization | Computer by DevRev | DevRev" }, { - "id": "ART-5010_KNOWLEDGE_NODE-32", - "text": "[Marketplace](https://marketplace.devrev.ai/)\\n\\nResources\\n\\n* [Blog](/blog)\\n* [Our Customers](/case-study)\\n* [Snap-In Extensions](https://developer.devrev.ai/public/snapin-development/concepts)\\n* [DevRevU training](/docs/DevRevU)\\n* [Documentation](https://docs.devrev.ai/)\\n* [API References](https://docs.devrev.ai/api/)\\n\\nCompany\\n\\n* [About](/about)\\n* [Events](/events)\\n* [Careers](/careers)\\n* [What Why How](/what-why-how)\\n\\nInitiatives\\n\\n* [Partner Program](/partners)\\n* [Startups", - "title": "Subtype Migration | Automate | Snap-ins | DevRev" + "id": "ART-12390_KNOWLEDGE_NODE-28", + "text": "like title, description, start\\\\_date, attendees, etc. * subtype: (Optional) Meeting subtype * apps: (Optional) Related apps * app\\\\_custom\\\\_fields: (Optional) Custom fields | Created meeting object |\\n| Create Opportunity | Creates a new opportunity in DevRev. | * Opportunity details like title, body, applies\\\\_to\\\\_part, etc. * subtype: (Optional) Opportunity subtype * apps: (Optional) Related apps * app\\\\_custom\\\\_fields: (Optional) Custom fields | Created opportunity object |\\n| Create", + "title": "Workflow action library | Workflows | Computer by DevRev | DevRev" }, { - "id": "ART-4116_KNOWLEDGE_NODE-10", - "text": "Agents?](https://devrev.ai/what-are-ai-agents)\\n * [What is Agentic AI?](https://devrev.ai/what-is-agentic-ai)\\n * [What is Enterprise Search?](https://devrev.ai/what-is-enterprise-search)\\n * [What is Conversational AI?](https://devrev.ai/what-is-conversational-ai)\\n\\n[](https://devrev.ai)\\n\\n[](https://www.linkedin.com/company/devrev)[](https://medium.com/devrev)[](https://twitter.com/devrev)\\n\\n[System Status](https://devrev.ai/status)\\n\\n\\xc2\\xa9 2025 DevRev", - "title": "Prepare-Update Schemas Subtypes (Beta) \u2014 DevRev | Docs" + "id": "ART-17218_KNOWLEDGE_NODE-13", + "text": "will be defined in DevRev and a **Subtype** will automatically be created. For more details on customization concepts, please refer to the\\n[Customization](/public/guides/object-customization) and [Custom Objects](/public/guides/custom-objects) documentation.\\n\\nThe field mapping works the same as for the stock DevRev types, with the difference being that there are significantly fewer fields to map. All the unmapped fields of the external record type will be created as custom", + "title": "Initial domain mapping | DevRev | Docs" }, { - "id": "ART-1593_KNOWLEDGE_NODE-318", - "text": "subtype \" : \" string \" , 35 \" tags \" : [ 36 { 37 \" tag \" : { 38 \" name \" : \" string \" , 39 \" display_id \" : \" string \" , 40 \" id \" : \" string \" 41 } , 42 \" value \" : \" string \" 43 } 44 ] , 45 \" created_by \" : { 46 \" type \" : \" dev_user \" , 47 \" display_name \" : \" string \" , 48 \" display_picture \" : { 49 \" display_id \" : \" string \" , 50 \" id \" : \" string \" 51 } , 52 \" email \" : \" string \" , 53 \" full_name \" : \" string \" , 54 \" state \" : \" active \" , 55 \" display_id \" : \" string \" , 56 \" id \" : \"", - "title": "Get \u2014 DevRev | Docs" + "id": "ART-12390_KNOWLEDGE_NODE-27", + "text": "applies\\\\_to\\\\_part, etc. * subtype: (Optional) Incident subtype * apps: (Optional) Related apps * app\\\\_custom\\\\_fields: (Optional) Custom fields | Created incident object |\\n| Create Issue | Creates a new issue in DevRev. | * Issue details like title, body, priority\\\\_v2, etc. * subtype: (Optional) Issue subtype * apps: (Optional) Related apps * app\\\\_custom\\\\_fields: (Optional) Custom fields | Created issue object |\\n| Create Meeting | Creates a new meeting in DevRev. | * Meeting details", + "title": "Workflow action library | Workflows | Computer by DevRev | DevRev" }, { - "id": "ART-1957_KNOWLEDGE_NODE-24", - "text": "subtype](#add-a-new-subtype)\\n\\n1. [Documentation](/docs)\\n3. [Computer by DevRev](/docs/intro)\\n[Object customization](/docs/product/object-customization)\\n\\nObject customization\\n====================\\n\\nDevRev powers your organization with the ability to customize DevRev objects for your organization\\'s needs. You can add custom fields to the objects along with the pre-existing fields or add new subtypes to the objects which helps you extend an object\\'s capabilities.\\nObjects are the core", - "title": "Object customization | Computer by DevRev | DevRev" + "id": "ART-1607_KNOWLEDGE_NODE-223", + "text": "Reference customization Subtypes List.\\n\\nGET https:// api.devrev.ai / schemas.subtypes.list\\nLists subtypes.\\nQuery parameters.\\n\\nleaf_type string Optional\\nLeaf type for which subtypes are required.\\nleaf_types string Optional\\nList of leaf types for which subtypes are required.\\nResponse.\\n\\nThis endpoint returns an object.\\nsubtypes list of objects\\nList of subtypes.\\nShow 4 properties\\nAPI Reference customization Subtypes List Post.\\n\\nPOST https:// api.devrev.ai /", + "title": "Get Post \u2014 DevRev | Docs" }, { - "id": "ART-5010_KNOWLEDGE_NODE-2", - "text": "[Object customization](/docs/product/object-customization)\\n + [Glossary \\xe2\\x86\\x97\\xef\\xb8\\x8f](https://support.devrev.ai/devrev/article/ART-16784-glossary)\\n + [Search](/docs/product/search)\\n + [Workflows](/docs/product/workflow-engine)\\n\\n - [Workflow action library](/docs/product/action-library)\\n - [Triggers](/docs/product/trigger-library)\\n - [Conversational workflows](/docs/product/conversational-workflows)\\n - [Workflow management](/docs/product/workflow-management)\\n", - "title": "Subtype Migration | Automate | Snap-ins | DevRev" + "id": "ART-1605_KNOWLEDGE_NODE-223", + "text": "Reference customization Subtypes List.\\n\\nGET https:// api.devrev.ai / schemas.subtypes.list\\nLists subtypes.\\nQuery parameters.\\n\\nleaf_type string Optional\\nLeaf type for which subtypes are required.\\nleaf_types string Optional\\nList of leaf types for which subtypes are required.\\nResponse.\\n\\nThis endpoint returns an object.\\nsubtypes list of objects\\nList of subtypes.\\nShow 4 properties\\nAPI Reference customization Subtypes List Post.\\n\\nPOST https:// api.devrev.ai /", + "title": "Create \u2014 DevRev | Docs" }, { - "id": "ART-5010_KNOWLEDGE_NODE-4", - "text": "insights](/docs/dashboards/conversation-insights)\\n - [Conversation-SLA Analytics](/docs/dashboards/conversation-sla-analytics)\\n - [Conversation-Team Performance](/docs/dashboards/conversation-team-performance)\\n - [Ticket insights](/docs/dashboards/ticket-insights)\\n - [Ticket-SLA Analytics](/docs/dashboards/ticket-sla-analytics)\\n - [Ticket-Team Performance](/docs/dashboards/ticket-team-performance)\\n + [Conversations](/docs/product/conversation)\\n\\n - [Conversation to", - "title": "Subtype Migration | Automate | Snap-ins | DevRev" + "id": "ART-1822_KNOWLEDGE_NODE-223", + "text": "Reference customization Subtypes List.\\n\\nGET https:// api.devrev.ai / schemas.subtypes.list\\nLists subtypes.\\nQuery parameters.\\n\\nleaf_type string Optional\\nLeaf type for which subtypes are required.\\nleaf_types string Optional\\nList of leaf types for which subtypes are required.\\nResponse.\\n\\nThis endpoint returns an object.\\nsubtypes list of objects\\nList of subtypes.\\nShow 4 properties\\nAPI Reference customization Subtypes List Post.\\n\\nPOST https:// api.devrev.ai /", + "title": "Create \u2014 DevRev | Docs" }, { - "id": "ART-5010_KNOWLEDGE_NODE-33", - "text": "Program](/startups)\\n* [Gr.ai.ce](/graice)\\n\\n* [Security](https://security.devrev.ai/)\\n* [SLA](/legal/sla)\\n* [DPA](/legal/dpa)\\n* [Subprocessors](/security/sub-processors)\\n* [Cookie Policy](/legal/cookie-policy)\\n* [Privacy Policy](/legal/privacy-policy)\\n* [Terms of Service](/legal/terms-of-service)\\n\\n[System Status](/status)\\n\\n\\xc2\\xa9 2025 DevRev Inc.'", - "title": "Subtype Migration | Automate | Snap-ins | DevRev" + "id": "ART-1306_KNOWLEDGE_NODE-228", + "text": "Reference customization Subtypes List.\\n\\nGET https:// api.devrev.ai / schemas.subtypes.list\\nLists subtypes.\\nQuery parameters.\\n\\nleaf_type string Optional\\nLeaf type for which subtypes are required.\\nleaf_types string Optional\\nList of leaf types for which subtypes are required.\\nResponse.\\n\\nThis endpoint returns an object.\\nsubtypes list of objects\\nList of subtypes.\\nShow 4 properties\\nAPI Reference customization Subtypes List Post.\\n\\nPOST https:// api.devrev.ai /", + "title": "List \u2014 DevRev | Docs" }, { - "id": "ART-4116_KNOWLEDGE_NODE-8", - "text": "[About](https://devrev.ai/about)\\n * [People](https://devrev.ai/people)\\n * [Careers](https://devrev.ai/careers)\\n * [Places](https://devrev.ai/places)\\n * [Invest](https://revd.devrev.ai/)\\n * [What Why How](https://devrev.ai/what-why-how)\\n\\nConnect\\n\\n * [Contact ](mailto:humansofdevrev@devrev.ai)\\n * [Instagram ](https://www.instagram.com/devrev)\\n * [Medium ](https://medium.com/devrev)\\n * [Linkedin ](https://www.linkedin.com/company/devrev)\\n * [X (formerly", - "title": "Prepare-Update Schemas Subtypes (Beta) \u2014 DevRev | Docs" + "id": "ART-1595_KNOWLEDGE_NODE-223", + "text": "Reference customization Subtypes List.\\n\\nGET https:// api.devrev.ai / schemas.subtypes.list\\nLists subtypes.\\nQuery parameters.\\n\\nleaf_type string Optional\\nLeaf type for which subtypes are required.\\nleaf_types string Optional\\nList of leaf types for which subtypes are required.\\nResponse.\\n\\nThis endpoint returns an object.\\nsubtypes list of objects\\nList of subtypes.\\nShow 4 properties\\nAPI Reference customization Subtypes List Post.\\n\\nPOST https:// api.devrev.ai /", + "title": "List \u2014 DevRev | Docs" } ] }, @@ -2748,54 +2748,54 @@ "query": "DevRev Platform Orientation & Navigation Guide video login options", "retrievals": [ { - "id": "ART-1944_KNOWLEDGE_NODE-0", - "text": "b\"Product Platform Solutions Marketplace Company Resources Pricing\\n\\nLogin Book a demo\\nProduct Platform Solutions Marketplace Company Resources Pricing\\nLogin Book a demo\\nSearch CTRL + K\\n\\nIntroduction AgentOS platform\\n\\nCore concepts Apps Groups Parts & trails Vistas Vista Reports\\nTasks Updates Customer email notifications Roles Default privileges by group\\nAccess control Object customization Glossary Search People insights Workflow Templates Accessing DevRev External identity provider", - "title": "DevRev Documentation" + "id": "ART-15701_KNOWLEDGE_NODE-6", + "text": "Option: Keep it as default i.e. allow both incoming and outgoing calls to truly experience the features provided by DevRev integration.\\n\\nYou can customise data storage options here.Recommended Option: Keep this as default and click on Next.\\n\\nReview the details and click on Create Instance.\\n\\nUse the Emergency Access to login the first time to setup the instance. If you are an administrator, you can directly use the access URL to login.\\n\\nYou can directly follow the guide available at home", + "title": "Amazon Connect Telephony Integration Guide" }, { - "id": "ART-2076_KNOWLEDGE_NODE-2", - "text": "applications](https://rise.articulate.com/share/yTvcdwN0dMgzhiU_Kgbbs2t8lfkpnC5O)[![]()\\n\\nDevRev: Admin management and set-up\\n\\nSet up, manage, and streamline workflows for smooth operations](https://devrevu.reach360.com/share/course/d238d6fd-ab6a-41b3-a99b-44e1d2a8d221)\\n\\nExplore more courses\\n--------------------\\n\\nDiscover more courses to expand your DevRev skills and continue your learning journey\\n\\n[![]()\\n\\nDevRev platform fundamentals\\n\\nYour first step to navigating and mastering", - "title": "DevRev University" + "id": "ART-2004_KNOWLEDGE_NODE-0", + "text": "b'Snap-ins | DevRev\\n\\n* Computer\\n* Resources\\n* [Our Customers](/case-study)\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](/request-a-demo)\\n\\nComputer\\n\\nResources\\n\\n[Our Customers](/case-study)\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](/request-a-demo)\\n\\nSearch\\n\\n`CMD`\\xc2\\xa0+\\xc2\\xa0`K`\\n\\n* [Introduction](/docs)\\n* [Computer by DevRev](/docs/intro)\\n\\n + [Core concepts](/docs/product/core)\\n + [Apps](/docs/product/apps)\\n + [Groups](/docs/product/groups)\\n +", + "title": "Snap-ins | DevRev" }, { - "id": "ART-4179_KNOWLEDGE_NODE-2", - "text": "applications](https://rise.articulate.com/share/yTvcdwN0dMgzhiU_Kgbbs2t8lfkpnC5O)[![]()\\n\\nDevRev: Admin management and set-up\\n\\nSet up, manage, and streamline workflows for smooth operations](https://devrevu.reach360.com/share/course/d238d6fd-ab6a-41b3-a99b-44e1d2a8d221)\\n\\nExplore more courses\\n--------------------\\n\\nDiscover more courses to expand your DevRev skills and continue your learning journey\\n\\n[![]()\\n\\nDevRev platform fundamentals\\n\\nYour first step to navigating and mastering", - "title": "DevRev University" + "id": "ART-2819_KNOWLEDGE_NODE-0", + "text": "b\"Exotel | Integrate | Snap-ins | DevRev\\n\\n* Computer\\n* Resources\\n* [Our Customers](/case-study)\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](/request-a-demo)\\n\\nComputer\\n\\nResources\\n\\n[Our Customers](/case-study)\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](/request-a-demo)\\n\\nSearch\\n\\n`CMD`\\xc2\\xa0+\\xc2\\xa0`K`\\n\\n* [Introduction](/docs)\\n* [Computer by DevRev](/docs/intro)\\n\\n + [Core concepts](/docs/product/core)\\n + [Apps](/docs/product/apps)\\n +", + "title": "Exotel | Integrate | Snap-ins | DevRev" }, { - "id": "ART-2666_KNOWLEDGE_NODE-27", - "text": "DevRev's left navigation is designed to provide a more customizable and intuitive navigation experience. This update introduces new sections for better organization, enhanced customization capabilities, and a dedicated **Explore** page for managing views, dashboards, and sprint boards.\\n\\nWhen existing users log in, a prompt appears to guide them in migrating to the new left navigation. Follow the on-screen instructions to complete the migration and begin customizing your experience.\\n\\n## Key", - "title": "October 5: Left navigation | Changelog | DevRev" + "id": "ART-2023_KNOWLEDGE_NODE-0", + "text": "b'Integrate | Snap-ins | DevRev\\n\\n* Computer\\n* Resources\\n* [Our Customers](/case-study)\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](/request-a-demo)\\n\\nComputer\\n\\nResources\\n\\n[Our Customers](/case-study)\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](/request-a-demo)\\n\\nSearch\\n\\n`CTRL`\\xc2\\xa0+\\xc2\\xa0`K`\\n\\n* [Introduction](/docs)\\n* [Computer by DevRev](/docs/intro)\\n\\n + [Core concepts](/docs/product/core)\\n + [Apps](/docs/product/apps)\\n +", + "title": "Integrate | Snap-ins | DevRev" }, { - "id": "ART-1362_KNOWLEDGE_NODE-15", - "text": "Inc.\\n\\n[](https://devrev.ai)\\n\\n * Product\\n * Platform\\n * Solutions\\n * Marketplace\\n * Company\\n * Resources\\n * [Pricing](https://devrev.ai/pricing)\\n\\n __\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](https://devrev.ai/request-a-demo)\\n\\n[](https://devrev.ai)\\n\\n __\\n\\nProduct __\\n\\nPlatform __\\n\\nSolutions __\\n\\nMarketplace __\\n\\nCompany __\\n\\nResources __\\n\\n[Pricing](https://devrev.ai/pricing)\\n\\n[Login](https://app.devrev.ai/login)[Book a", - "title": "Authentication \u2014 DevRev | Docs" + "id": "ART-2031_KNOWLEDGE_NODE-0", + "text": "b\"Harness | Integrate | Snap-ins | DevRev\\n\\n* Computer\\n* Resources\\n* [Our Customers](/case-study)\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](/request-a-demo)\\n\\nComputer\\n\\nResources\\n\\n[Our Customers](/case-study)\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](/request-a-demo)\\n\\nSearch\\n\\n`CTRL`\\xc2\\xa0+\\xc2\\xa0`K`\\n\\n* [Introduction](/docs)\\n* [Computer by DevRev](/docs/intro)\\n\\n + [Core concepts](/docs/product/core)\\n + [Apps](/docs/product/apps)\\n +", + "title": "Harness | Integrate | Snap-ins | DevRev" }, { - "id": "ART-12447_KNOWLEDGE_NODE-14", - "text": "Inc.\\n\\n[](https://devrev.ai)\\n\\n * Product\\n * Platform\\n * Solutions\\n * Marketplace\\n * Company\\n * Resources\\n * [Pricing](https://devrev.ai/pricing)\\n\\n __\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](https://devrev.ai/request-a-demo)\\n\\n[](https://devrev.ai)\\n\\n __\\n\\nProduct __\\n\\nPlatform __\\n\\nSolutions __\\n\\nMarketplace __\\n\\nCompany __\\n\\nResources __\\n\\n[Pricing](https://devrev.ai/pricing)\\n\\n[Login](https://app.devrev.ai/login)[Book a", - "title": "Quickstart guide \u2014 DevRev | Docs" + "id": "ART-2035_KNOWLEDGE_NODE-0", + "text": "b\"Slack | Integrate | Snap-ins | DevRev\\n\\n* Computer\\n* Resources\\n* [Our Customers](/case-study)\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](/request-a-demo)\\n\\nComputer\\n\\nResources\\n\\n[Our Customers](/case-study)\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](/request-a-demo)\\n\\nSearch\\n\\n`CTRL`\\xc2\\xa0+\\xc2\\xa0`K`\\n\\n* [Introduction](/docs)\\n* [Computer by DevRev](/docs/intro)\\n\\n + [Core concepts](/docs/product/core)\\n + [Apps](/docs/product/apps)\\n +", + "title": "Slack | Integrate | Snap-ins | DevRev" }, { - "id": "ART-12450_KNOWLEDGE_NODE-13", - "text": "Company\\n * Resources\\n * [Pricing](https://devrev.ai/pricing)\\n\\n __\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](https://devrev.ai/request-a-demo)\\n\\n[](https://devrev.ai)\\n\\n __\\n\\nProduct __\\n\\nPlatform __\\n\\nSolutions __\\n\\nMarketplace __\\n\\nCompany __\\n\\nResources __\\n\\n[Pricing](https://devrev.ai/pricing)\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](https://devrev.ai/request-a-demo)\\n\\n'", - "title": "Quickstart guide \u2014 DevRev | Docs" + "id": "ART-2036_KNOWLEDGE_NODE-0", + "text": "b'SendSafely | Integrate | Snap-ins | DevRev\\n\\n* Computer\\n* Resources\\n* [Our Customers](/case-study)\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](/request-a-demo)\\n\\nComputer\\n\\nResources\\n\\n[Our Customers](/case-study)\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](/request-a-demo)\\n\\nSearch\\n\\n`CMD`\\xc2\\xa0+\\xc2\\xa0`K`\\n\\n* [Introduction](/docs)\\n* [Computer by DevRev](/docs/intro)\\n\\n + [Core concepts](/docs/product/core)\\n + [Apps](/docs/product/apps)\\n +", + "title": "SendSafely | Integrate | Snap-ins | DevRev" }, { - "id": "ART-4256_KNOWLEDGE_NODE-6", - "text": "the user logs in. If you have the user information available at app launch, call the function after the `DevRev.configure(appID:)` method.\\n\\n#####\\n\\nOn iOS, if you haven\\xe2\\x80\\x99t previously identified the user, the DevRev SDK will automatically create an anonymous user for you immediately after the SDK is configured.\\n\\n#####\\n\\nThe `Identity` structure allows for custom fields in the user, organization, and account traits. These fields must be configured through the DevRev app before", - "title": "DevRev SDK for React Native \u2014 DevRev | Docs" + "id": "ART-2043_KNOWLEDGE_NODE-0", + "text": "b'Glean | Integrate | Snap-ins | DevRev\\n\\n* Computer\\n* Resources\\n* [Our Customers](/case-study)\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](/request-a-demo)\\n\\nComputer\\n\\nResources\\n\\n[Our Customers](/case-study)\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](/request-a-demo)\\n\\nSearch\\n\\n`CTRL`\\xc2\\xa0+\\xc2\\xa0`K`\\n\\n* [Introduction](/docs)\\n* [Computer by DevRev](/docs/intro)\\n\\n + [Core concepts](/docs/product/core)\\n + [Apps](/docs/product/apps)\\n +", + "title": "Glean | Integrate | Snap-ins | DevRev" }, { - "id": "ART-12475_KNOWLEDGE_NODE-0", - "text": "b'This document serves as a guide for migrating from UserExperior ( plug.devrev.ai ) to DevRev ( app.devrev.ai ).\\n\\nLog in to your DevRev account at app.devrev.ai/login .\\n\\nPin the relevant views in the left navigation panel for Session Analytics. The views to pin are Session Replays , Session Analytics: Web , and Session Analytics: Mobile . For detailed instructions on this process, click here .\\n\\nLocate the SDK integration key by navigating to Settings > Support > Session Replays", - "title": "Migrating from UserExperior to DevRev" + "id": "ART-2037_KNOWLEDGE_NODE-0", + "text": "b'GitHub | Integrate | Snap-ins | DevRev\\n\\n* Computer\\n* Resources\\n* [Our Customers](/case-study)\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](/request-a-demo)\\n\\nComputer\\n\\nResources\\n\\n[Our Customers](/case-study)\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](/request-a-demo)\\n\\nSearch\\n\\n`CMD`\\xc2\\xa0+\\xc2\\xa0`K`\\n\\n* [Introduction](/docs)\\n* [Computer by DevRev](/docs/intro)\\n\\n + [Core concepts](/docs/product/core)\\n + [Apps](/docs/product/apps)\\n +", + "title": "GitHub | Integrate | Snap-ins | DevRev" }, { - "id": "ART-2662_KNOWLEDGE_NODE-0", - "text": "b'DevRev Documentation\\n\\n* Computer\\n* Resources\\n* [Our Customers](/case-study)\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](/request-a-demo)\\n\\nComputer\\n\\nResources\\n\\n[Our Customers](/case-study)\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](/request-a-demo)\\n\\nSearch\\n\\n`CTRL`\\xc2\\xa0+\\xc2\\xa0`K`\\n\\n* [Introduction](/docs)\\n* [Computer by DevRev](/docs/intro)\\n\\n + [Core concepts](/docs/product/core)\\n + [Apps](/docs/product/apps)\\n + [Groups](/docs/product/groups)\\n +", - "title": "DevRev Documentation" + "id": "ART-2041_KNOWLEDGE_NODE-0", + "text": "b'Qase | Integrate | Snap-ins | DevRev\\n\\n* Computer\\n* Resources\\n* [Our Customers](/case-study)\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](/request-a-demo)\\n\\nComputer\\n\\nResources\\n\\n[Our Customers](/case-study)\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](/request-a-demo)\\n\\nSearch\\n\\n`CTRL`\\xc2\\xa0+\\xc2\\xa0`K`\\n\\n* [Introduction](/docs)\\n* [Computer by DevRev](/docs/intro)\\n\\n + [Core concepts](/docs/product/core)\\n + [Apps](/docs/product/apps)\\n +", + "title": "Qase | Integrate | Snap-ins | DevRev" } ] }, @@ -2804,9 +2804,14 @@ "query": "change subtype of ticket error something went wrong", "retrievals": [ { - "id": "ART-5010_KNOWLEDGE_NODE-5", - "text": "ticket conversion](/docs/product/conversation-ticket)\\n + [Tickets](/docs/product/tickets)\\n + [Routing](/docs/product/routing)\\n + [Support best practices](/docs/product/support-bp)\\n + [Customer portal](/docs/product/support-portal)\\n + [Questions & answers](/docs/product/qa)\\n + [Knowledge Base](/docs/product/knowledge-base)\\n\\n - [Articles](/docs/product/articles)\\n - [Collections](/docs/product/collection)\\n + [Turing AI agent](/docs/product/conversational-bot)\\n\\n - [Best", - "title": "Subtype Migration | Automate | Snap-ins | DevRev" + "id": "ART-15664_KNOWLEDGE_NODE-14", + "text": "> | \"leaf_type\": \"issue\", |\\n| > | \"subtype\": \"social_media\" |\\n| > | } |\\n| > | ], |\\n| > | \"target_types\": [ |\\n| > | { |\\n| > | \"leaf_type\": \"ticket\" |\\n| > | } |\\n| > | ], |\\n| > | \"forward_name\": \"is related to\", |\\n| > | \"backward_name\": \"is related to\" |\\n| > | }\\' |\\n```\\n\\nThis configuration:\\n\\n* Allows issues of subtype \\xe2\\x80\\x9csocial\\\\_media\\xe2\\x80\\x9d to be linked to tickets\\n* Rejects attempts to link issues with no subtype or with other subtypes\\n\\n##### \\n\\nThe subtype", + "title": "Links | DevRev | Docs" + }, + { + "id": "ART-1959_KNOWLEDGE_NODE-34", + "text": "subtype: :\\n```\\n```\\n\\n**Examples**\\n\\nSearch for tickets related to access issues with tenant field escalated:\\n\\n```\\n```\\n1 tnt__escalated:true access issues\\n```\\n```\\n\\nSearch for bugs related to access issues with subtype field customer\\\\_impact:\\n\\n```\\n```\\n1 subtype:Bug ctype__customer_impact:true access issues\\n```\\n```\\n\\nSearch across multiple subtypes for tickets related to access issues:\\n\\n```\\n```\\n1 subtype:Bug,Events access", + "title": "Search | Computer by DevRev | DevRev" }, { "id": "ART-1979_KNOWLEDGE_NODE-49", @@ -2814,44 +2819,39 @@ "title": "Tickets | Computer for Support Teams | DevRev" }, { - "id": "ART-5010_KNOWLEDGE_NODE-26", - "text": "**Work Item Type**: Select either \"ticket\" or \"issue\" based on the type of work items you want to migrate\\n * **Source Subtype**: Enter the name of the current subtype from which you want to migrate work items\\n * **Target Subtype**: Enter the name of the target subtype to which you want to migrate work items\\n * **Field Mappings**: Enter each mapping as source\\\\_field, target\\\\_field, one mapping per line\\n\\n ![]()\\n\\n Field names and subtype names must exactly match how they appear", - "title": "Subtype Migration | Automate | Snap-ins | DevRev" - }, - { - "id": "ART-1979_KNOWLEDGE_NODE-24", - "text": "[Subtypes](#subtypes)\\n* [Viewing attachments on tickets](#viewing-attachments-on-tickets)\\n* [Turing suggests](#turing-suggests)\\n* [Duplicate ticket merging](#duplicate-ticket-merging)\\n* [Merging guidelines](#merging-guidelines)\\n* [Merge settings](#merge-settings)\\n* [Merge tickets](#merge-tickets)\\n* [Post-merge conditions](#postmerge-conditions)\\n* [Follow up tickets](#follow-up-tickets)\\n* [Internal Tickets](#internal-tickets)\\n\\n1. [Documentation](/docs)\\n3. [Computer for Support", - "title": "Tickets | Computer for Support Teams | DevRev" + "id": "ART-15664_KNOWLEDGE_NODE-13", + "text": "\\n\\nYou may want to restrict links to specific subtypes of objects. For example, only allowing issues\\nof a particular subtype to be linked to tickets.\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl --location \\'https://api.devrev.ai/link-types.custom.create\\' \\\\ |\\n| > | --header \\'Content-Type: application/json\\' \\\\ |\\n| > | --header \\'Authorization: Bearer \\' \\\\ |\\n| > | --data \\'{ |\\n| > | \"name\": \"Link between social media issues and tickets\", |\\n| > | \"source_types\": [ |\\n| > | { |\\n|", + "title": "Links | DevRev | Docs" }, { - "id": "ART-1959_KNOWLEDGE_NODE-34", - "text": "subtype: :\\n```\\n```\\n\\n**Examples**\\n\\nSearch for tickets related to access issues with tenant field escalated:\\n\\n```\\n```\\n1 tnt__escalated:true access issues\\n```\\n```\\n\\nSearch for bugs related to access issues with subtype field customer\\\\_impact:\\n\\n```\\n```\\n1 subtype:Bug ctype__customer_impact:true access issues\\n```\\n```\\n\\nSearch across multiple subtypes for tickets related to access issues:\\n\\n```\\n```\\n1 subtype:Bug,Events access", - "title": "Search | Computer by DevRev | DevRev" + "id": "ART-1782_KNOWLEDGE_NODE-447", + "text": "warning\\nticket.source_channel string Optional\\nFilters for tickets with any of the provided source channels.\\nticket.subtype string Optional\\nFilters for tickets with any of the provided subtypes.\\ntype enum Optional\\nFilters for work of the provided types.\\nAllowed values: issue opportunity task ticket\\nResponse.\\n\\nThis endpoint returns an object.\\nworks list of objects\\nThe resulting collection of work items.\\nShow 4 variants\\nAPI Reference works Export Post.\\n\\nPOST https:// api.devrev.ai", + "title": "List Post \u2014 DevRev | Docs" }, { - "id": "ART-1566_KNOWLEDGE_NODE-521", - "text": "response.\\n\\nticket.rev_org string Optional\\n\\nFilters for tickets that are associated with any of the provided Rev organizations.\\n\\nticket.severity enum Optional\\n\\nFilters for tickets with any of the provided severities.\\n\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\n\\nFilters for records with any of the provided SLA stages.\\n\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\n\\nFilters for tickets with any", - "title": "Transition (Beta) \u2014 DevRev | Docs" + "id": "ART-1826_KNOWLEDGE_NODE-448", + "text": "warning\\nticket.source_channel string Optional\\nFilters for tickets with any of the provided source channels.\\nticket.subtype string Optional\\nFilters for tickets with any of the provided subtypes.\\ntype enum Optional\\nFilters for work of the provided types.\\nAllowed values: issue opportunity task ticket\\nResponse.\\n\\nThis endpoint returns an object.\\nworks list of objects\\nThe resulting collection of work items.\\nShow 4 variants\\nAPI Reference works Export Post.\\n\\nPOST https:// api.devrev.ai", + "title": "Get Post \u2014 DevRev | Docs" }, { - "id": "ART-15664_KNOWLEDGE_NODE-14", - "text": "> | \"leaf_type\": \"issue\", |\\n| > | \"subtype\": \"social_media\" |\\n| > | } |\\n| > | ], |\\n| > | \"target_types\": [ |\\n| > | { |\\n| > | \"leaf_type\": \"ticket\" |\\n| > | } |\\n| > | ], |\\n| > | \"forward_name\": \"is related to\", |\\n| > | \"backward_name\": \"is related to\" |\\n| > | }\\' |\\n```\\n\\nThis configuration:\\n\\n* Allows issues of subtype \\xe2\\x80\\x9csocial\\\\_media\\xe2\\x80\\x9d to be linked to tickets\\n* Rejects attempts to link issues with no subtype or with other subtypes\\n\\n##### \\n\\nThe subtype", - "title": "Links | DevRev | Docs" + "id": "ART-1609_KNOWLEDGE_NODE-450", + "text": "warning\\nticket.source_channel string Optional\\nFilters for tickets with any of the provided source channels.\\nticket.subtype string Optional\\nFilters for tickets with any of the provided subtypes.\\ntype enum Optional\\nFilters for work of the provided types.\\nAllowed values: issue opportunity task ticket\\nResponse.\\n\\nThis endpoint returns an object.\\nworks list of objects\\nThe resulting collection of work items.\\nShow 4 variants\\nAPI Reference works Export Post.\\n\\nPOST https:// api.devrev.ai", + "title": "List Post \u2014 DevRev | Docs" }, { - "id": "ART-5010_KNOWLEDGE_NODE-13", - "text": "group](/docs/automations/set-user-preference)\\n - [SLA status change Slack notifier](/docs/automations/sla-change-notifier)\\n - [Slash commands](/docs/automations/slash-commands)\\n - [Spam Shield](/docs/automations/spam-shield)\\n - [Subtype Migration](/docs/automations/subtype-migration)\\n - [Ticket age in engineering](/docs/automations/ticket-age-in-engineering)\\n - [Ticket issue field migrator](/docs/automations/ticket-issue-field-migrator)\\n - [Ticket", - "title": "Subtype Migration | Automate | Snap-ins | DevRev" + "id": "ART-1597_KNOWLEDGE_NODE-452", + "text": "warning\\nticket.source_channel string Optional\\nFilters for tickets with any of the provided source channels.\\nticket.subtype string Optional\\nFilters for tickets with any of the provided subtypes.\\ntype enum Optional\\nFilters for work of the provided types.\\nAllowed values: issue opportunity task ticket\\nResponse.\\n\\nThis endpoint returns an object.\\nworks list of objects\\nThe resulting collection of work items.\\nShow 4 variants\\nAPI Reference works Export Post.\\n\\nPOST https:// api.devrev.ai", + "title": "Update \u2014 DevRev | Docs" }, { - "id": "ART-2874_KNOWLEDGE_NODE-5", - "text": "ticket conversion](/docs/product/conversation-ticket)\\n + [Tickets](/docs/product/tickets)\\n + [Routing](/docs/product/routing)\\n + [Support best practices](/docs/product/support-bp)\\n + [Customer portal](/docs/product/support-portal)\\n + [Questions & answers](/docs/product/qa)\\n + [Knowledge Base](/docs/product/knowledge-base)\\n\\n - [Articles](/docs/product/articles)\\n - [Collections](/docs/product/collection)\\n + [Turing AI agent](/docs/product/conversational-bot)\\n\\n - [Best", - "title": "Ticket issue field migrator | Automate | Snap-ins | DevRev" + "id": "ART-1822_KNOWLEDGE_NODE-448", + "text": "warning\\nticket.source_channel string Optional\\nFilters for tickets with any of the provided source channels.\\nticket.subtype string Optional\\nFilters for tickets with any of the provided subtypes.\\ntype enum Optional\\nFilters for work of the provided types.\\nAllowed values: issue opportunity task ticket\\nResponse.\\n\\nThis endpoint returns an object.\\nworks list of objects\\nThe resulting collection of work items.\\nShow 4 variants\\nAPI Reference works Export Post.\\n\\nPOST https:// api.devrev.ai", + "title": "Create \u2014 DevRev | Docs" }, { - "id": "ART-1979_KNOWLEDGE_NODE-65", - "text": "conversion](/docs/product/conversation-ticket)[NextRouting](/docs/product/routing)\\n\\n#### On this page\\n\\n* [Attributes](#attributes)\\n* [Create a ticket](#create-a-ticket)\\n* [Tags](#tags)\\n* [Stages](#stages)\\n* [Subtypes](#subtypes)\\n* [Viewing attachments on tickets](#viewing-attachments-on-tickets)\\n* [Turing suggests](#turing-suggests)\\n* [Duplicate ticket merging](#duplicate-ticket-merging)\\n* [Merging guidelines](#merging-guidelines)\\n* [Merge settings](#merge-settings)\\n* [Merge", - "title": "Tickets | Computer for Support Teams | DevRev" + "id": "ART-1483_KNOWLEDGE_NODE-18", + "text": "the code\\n\\nUpdate the code in `src/functions/ticket_creator/index.ts` to reflect the behavior.\\n\\nFirstly, import the DevRev TypeScript SDK in the `index.ts` file\\n\\nindex.ts\\n\\n[code]\\n\\n 1| import {client, publicSDK} from \"@devrev/typescript-sdk\"; \\n ---|---\\n[/code] \\n \\nNext, update the `run` function in the hello-world example. Since the ticket gets created frequently, set some creation time in the title and the body. The example uses the part as `PROD-1` and keeps the owner as", + "title": "Using a snap-in to perform a DevRev action \u2014 DevRev | Docs" } ] }, @@ -2860,54 +2860,54 @@ "query": "Why would I use DevRev?", "retrievals": [ { - "id": "ART-1487_KNOWLEDGE_NODE-7", - "text": "Program](https://devrev.ai/startups)\\n\\nCompany\\n\\n * [About](https://devrev.ai/about)\\n * [People](https://devrev.ai/people)\\n * [Careers](https://devrev.ai/careers)\\n * [Places](https://devrev.ai/places)\\n * [Invest](https://revd.devrev.ai/)\\n * [What Why How](https://devrev.ai/what-why-how)\\n\\nConnect\\n\\n * [Contact ](mailto:humansofdevrev@devrev.ai)\\n * [Instagram ](https://www.instagram.com/devrev)\\n * [Medium ](https://medium.com/devrev)\\n * [Linkedin", - "title": "Install DevRev CLI \u2014 DevRev | Docs" + "id": "ART-16688_KNOWLEDGE_NODE-2", + "text": "to increase product velocity and reduce customer churn. DevRev is used by thousands of companies in search of low latency analytics and customizable LLMs to thrive in this era of GenAI. \\n \\nHeadquartered in Palo Alto, California, DevRev has offices in seven global locations. We have raised $100 million in funding from investors like Khosla Ventures and Mayfield at a $1.1 billion valuation. We are also honored to be named on the Forbes 2024 list of America\\xe2\\x80\\x99s Best Startup", + "title": "DevRev Careers | Marketing Designer, Digital & Print - Bengaluru" }, { - "id": "ART-12989_KNOWLEDGE_NODE-6", - "text": "[Documentation](https://docs.devrev.ai/)\\n * [API Reference](https://docs.devrev.ai/api/)\\n * [The Book of DevRev](https://thebook.devrev.ai/)\\n * [Partner Program](https://devrev.ai/partners)\\n * [Startup Program](https://devrev.ai/startups)\\n\\nCompany\\n\\n * [About](https://devrev.ai/about)\\n * [People](https://devrev.ai/people)\\n * [Careers](https://devrev.ai/careers)\\n * [Places](https://devrev.ai/places)\\n * [Invest](https://revd.devrev.ai/)\\n * [What Why", - "title": "Activate Dev Users \u2014 DevRev | Docs" + "id": "ART-16798_KNOWLEDGE_NODE-2", + "text": "to increase product velocity and reduce customer churn. DevRev is used by thousands of companies in search of low latency analytics and customizable LLMs to thrive in this era of GenAI. \\n \\nHeadquartered in Palo Alto, California, DevRev has offices in seven global locations. We have raised $100 million in funding from investors like Khosla Ventures and Mayfield at a $1.1 billion valuation. We are also honored to be named on the Forbes 2024 list of America\\xe2\\x80\\x99s Best Startup", + "title": "DevRev Careers | Partner Success Manager" }, { - "id": "ART-17231_KNOWLEDGE_NODE-157", - "text": "with](https://buildwithfern.com/?utm_campaign=buildWith&utm_medium=docs&utm_source=developer.devrev.ai)'", - "title": "Supported DevRev object types | DevRev | Docs" + "id": "ART-15590_KNOWLEDGE_NODE-2", + "text": "to increase product velocity and reduce customer churn. DevRev is used by thousands of companies in search of low latency analytics and customizable LLMs to thrive in this era of GenAI. \\n \\nHeadquartered in Palo Alto, California, DevRev has offices in seven global locations. We have raised $100 million in funding from investors like Khosla Ventures and Mayfield at a $1.1 billion valuation. We are also honored to be named on the Forbes 2024 list of America\\xe2\\x80\\x99s Best Startup", + "title": "DevRev Careers | GTM Finance Manager- FP&A" }, { - "id": "ART-1400_KNOWLEDGE_NODE-12", - "text": "[Documentation](https://docs.devrev.ai/)\\n * [API Reference](https://docs.devrev.ai/api/)\\n * [The Book of DevRev](https://thebook.devrev.ai/)\\n * [Partner Program](https://devrev.ai/partners)\\n * [Startup Program](https://devrev.ai/startups)\\n\\nCompany\\n\\n * [About](https://devrev.ai/about)\\n * [People](https://devrev.ai/people)\\n * [Careers](https://devrev.ai/careers)\\n * [Places](https://devrev.ai/places)\\n * [Invest](https://revd.devrev.ai/)\\n * [What Why", - "title": "Get Dev User \u2014 DevRev | Docs" + "id": "ART-15961_KNOWLEDGE_NODE-2", + "text": "to increase product velocity and reduce customer churn. DevRev is used by thousands of companies in search of low latency analytics and customizable LLMs to thrive in this era of GenAI. \\n \\nHeadquartered in Palo Alto, California, DevRev has offices in seven global locations. We have raised $100 million in funding from investors like Khosla Ventures and Mayfield at a $1.1 billion valuation. We are also honored to be named on the Forbes 2024 list of America\\xe2\\x80\\x99s Best Startup", + "title": "DevRev Careers | Senior Member of Technical Staff : Front-End" }, { - "id": "ART-13031_KNOWLEDGE_NODE-5", - "text": "[Documentation](https://docs.devrev.ai/)\\n * [API Reference](https://docs.devrev.ai/api/)\\n * [The Book of DevRev](https://thebook.devrev.ai/)\\n * [Partner Program](https://devrev.ai/partners)\\n * [Startup Program](https://devrev.ai/startups)\\n\\nCompany\\n\\n * [About](https://devrev.ai/about)\\n * [People](https://devrev.ai/people)\\n * [Careers](https://devrev.ai/careers)\\n * [Places](https://devrev.ai/places)\\n * [Invest](https://revd.devrev.ai/)\\n * [What Why", - "title": "Merge Rev Users \u2014 DevRev | Docs" + "id": "ART-15956_KNOWLEDGE_NODE-2", + "text": "to increase product velocity and reduce customer churn. DevRev is used by thousands of companies in search of low latency analytics and customizable LLMs to thrive in this era of GenAI. \\n \\nHeadquartered in Palo Alto, California, DevRev has offices in seven global locations. We have raised $100 million in funding from investors like Khosla Ventures and Mayfield at a $1.1 billion valuation. We are also honored to be named on the Forbes 2024 list of America\\xe2\\x80\\x99s Best Startup", + "title": "DevRev Careers | Member of Technical Staff: Front-End" }, { - "id": "ART-12988_KNOWLEDGE_NODE-7", - "text": "DevRev](https://thebook.devrev.ai/)\\n * [Partner Program](https://devrev.ai/partners)\\n * [Startup Program](https://devrev.ai/startups)\\n\\nCompany\\n\\n * [About](https://devrev.ai/about)\\n * [People](https://devrev.ai/people)\\n * [Careers](https://devrev.ai/careers)\\n * [Places](https://devrev.ai/places)\\n * [Invest](https://revd.devrev.ai/)\\n * [What Why How](https://devrev.ai/what-why-how)\\n\\nConnect\\n\\n * [Contact ](mailto:humansofdevrev@devrev.ai)\\n * [Instagram", - "title": "Get Dev Org \u2014 DevRev | Docs" + "id": "ART-12614_KNOWLEDGE_NODE-2", + "text": "to increase product velocity and reduce customer churn. DevRev is used by thousands of companies in search of low latency analytics and customizable LLMs to thrive in this era of GenAI. \\n \\nHeadquartered in Palo Alto, California, DevRev has offices in seven global locations. We have raised $100 million in funding from investors like Khosla Ventures and Mayfield at a $1.1 billion valuation. We are also honored to be named on the Forbes 2024 list of America\\xe2\\x80\\x99s Best Startup", + "title": "DevRev Careers | Solutions Engineer - Mumbai" }, { - "id": "ART-1487_KNOWLEDGE_NODE-10", - "text": "Status](https://devrev.ai/status)\\n\\n\\xc2\\xa9 2025 DevRev Inc.\\n\\n[](https://devrev.ai)\\n\\n * Product\\n * Platform\\n * Solutions\\n * Marketplace\\n * Company\\n * Resources\\n * [Pricing](https://devrev.ai/pricing)\\n\\n __\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](https://devrev.ai/request-a-demo)\\n\\n[](https://devrev.ai)\\n\\n __\\n\\nProduct __\\n\\nPlatform __\\n\\nSolutions __\\n\\nMarketplace __\\n\\nCompany __\\n\\nResources", - "title": "Install DevRev CLI \u2014 DevRev | Docs" + "id": "ART-15203_KNOWLEDGE_NODE-2", + "text": "to increase product velocity and reduce customer churn. DevRev is used by thousands of companies in search of low latency analytics and customizable LLMs to thrive in this era of GenAI. \\n \\nHeadquartered in Palo Alto, California, DevRev has offices in seven global locations. We have raised $100 million in funding from investors like Khosla Ventures and Mayfield at a $1.1 billion valuation. We are also honored to be named on the Forbes 2024 list of America\\xe2\\x80\\x99s Best Startup", + "title": "DevRev Careers | Senior Customer Success Manager" }, { - "id": "ART-1487_KNOWLEDGE_NODE-8", - "text": "](https://www.linkedin.com/company/devrev)\\n * [X (formerly Twitter)](https://twitter.com/devrev)\\n * [Gr.ai.ce](https://devrev.ai/graice)\\n\\nLegal\\n\\n * [Security](https://security.devrev.ai/)\\n * [SLA](https://devrev.ai/legal/sla)\\n * [DPA](https://devrev.ai/legal/dpa)\\n * [Subprocessors](https://devrev.ai/security/sub-processors)\\n * [Cookie Policy](https://devrev.ai/legal/cookie-policy)\\n * [Privacy Policy](https://devrev.ai/legal/privacy-policy)\\n * [Terms of", - "title": "Install DevRev CLI \u2014 DevRev | Docs" + "id": "ART-15592_KNOWLEDGE_NODE-2", + "text": "to increase product velocity and reduce customer churn. DevRev is used by thousands of companies in search of low latency analytics and customizable LLMs to thrive in this era of GenAI. \\n \\nHeadquartered in Palo Alto, California, DevRev has offices in seven global locations. We have raised $100 million in funding from investors like Khosla Ventures and Mayfield at a $1.1 billion valuation. We are also honored to be named on the Forbes 2024 list of America\\xe2\\x80\\x99s Best Startup", + "title": "DevRev Careers | Partner Solutions Engineer" }, { - "id": "ART-1487_KNOWLEDGE_NODE-11", - "text": "__\\n\\n[Pricing](https://devrev.ai/pricing)\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](https://devrev.ai/request-a-demo)\\n\\n'", - "title": "Install DevRev CLI \u2014 DevRev | Docs" + "id": "ART-12597_KNOWLEDGE_NODE-2", + "text": "to increase product velocity and reduce customer churn. DevRev is used by thousands of companies in search of low latency analytics and customizable LLMs to thrive in this era of GenAI. \\n \\nHeadquartered in Palo Alto, California, DevRev has offices in seven global locations. We have raised $100 million in funding from investors like Khosla Ventures and Mayfield at a $1.1 billion valuation. We are also honored to be named on the Forbes 2024 list of America\\xe2\\x80\\x99s Best Startup", + "title": "DevRev Careers | Member of Technical Staff: Front-End" }, { - "id": "ART-4096_KNOWLEDGE_NODE-14", - "text": "[Documentation](https://docs.devrev.ai/)\\n * [API Reference](https://docs.devrev.ai/api/)\\n * [The Book of DevRev](https://thebook.devrev.ai/)\\n * [Partner Program](https://devrev.ai/partners)\\n * [Startup Program](https://devrev.ai/startups)\\n\\nCompany\\n\\n * [About](https://devrev.ai/about)\\n * [People](https://devrev.ai/people)\\n * [Careers](https://devrev.ai/careers)\\n * [Places](https://devrev.ai/places)\\n * [Invest](https://revd.devrev.ai/)\\n * [What Why", - "title": "Create Rev User \u2014 DevRev | Docs" + "id": "ART-16686_KNOWLEDGE_NODE-2", + "text": "to increase product velocity and reduce customer churn. DevRev is used by thousands of companies in search of low latency analytics and customizable LLMs to thrive in this era of GenAI. \\n \\nHeadquartered in Palo Alto, California, DevRev has offices in seven global locations. We have raised $100 million in funding from investors like Khosla Ventures and Mayfield at a $1.1 billion valuation. We are also honored to be named on the Forbes 2024 list of America\\xe2\\x80\\x99s Best Startup", + "title": "DevRev Careers | Member of Product Management" } ] }, @@ -2916,54 +2916,54 @@ "query": "apply repeated multiple fields on tickets with one click", "retrievals": [ { - "id": "ART-3107_KNOWLEDGE_NODE-24", - "text": "existing tickets](#triggering-tag-checks-for-existing-tickets)\\n\\n1. [Documentation](/docs)\\n3. [Snap-ins](/docs/snapins)\\n[Automate](/docs/automate)\\n[Ticket Tagger](/docs/automations/ticket-tagger)\\n\\nTicket tagger\\n=============\\n\\nThe **Ticket Tagger** is an automation tool designed to streamline ticket\\nmanagement. It automatically assigns appropriate tags to tickets based on the\\ntags of the contact or their account.\\n\\nKey features\\n------------\\n\\n* Automatically tags tickets created by", - "title": "Ticket Tagger | Automate | Snap-ins | DevRev" - }, - { - "id": "ART-6175_KNOWLEDGE_NODE-5", - "text": "ticket conversion](/docs/product/conversation-ticket)\\n + [Tickets](/docs/product/tickets)\\n + [Routing](/docs/product/routing)\\n + [Support best practices](/docs/product/support-bp)\\n + [Customer portal](/docs/product/support-portal)\\n + [Questions & answers](/docs/product/qa)\\n + [Knowledge Base](/docs/product/knowledge-base)\\n\\n - [Articles](/docs/product/articles)\\n - [Collections](/docs/product/collection)\\n + [Turing AI agent](/docs/product/conversational-bot)\\n\\n - [Best", - "title": "Airtable | Automate | Snap-ins | DevRev" + "id": "ART-1483_KNOWLEDGE_NODE-18", + "text": "the code\\n\\nUpdate the code in `src/functions/ticket_creator/index.ts` to reflect the behavior.\\n\\nFirstly, import the DevRev TypeScript SDK in the `index.ts` file\\n\\nindex.ts\\n\\n[code]\\n\\n 1| import {client, publicSDK} from \"@devrev/typescript-sdk\"; \\n ---|---\\n[/code] \\n \\nNext, update the `run` function in the hello-world example. Since the ticket gets created frequently, set some creation time in the title and the body. The example uses the part as `PROD-1` and keeps the owner as", + "title": "Using a snap-in to perform a DevRev action \u2014 DevRev | Docs" }, { - "id": "ART-2874_KNOWLEDGE_NODE-5", - "text": "ticket conversion](/docs/product/conversation-ticket)\\n + [Tickets](/docs/product/tickets)\\n + [Routing](/docs/product/routing)\\n + [Support best practices](/docs/product/support-bp)\\n + [Customer portal](/docs/product/support-portal)\\n + [Questions & answers](/docs/product/qa)\\n + [Knowledge Base](/docs/product/knowledge-base)\\n\\n - [Articles](/docs/product/articles)\\n - [Collections](/docs/product/collection)\\n + [Turing AI agent](/docs/product/conversational-bot)\\n\\n - [Best", + "id": "ART-2874_KNOWLEDGE_NODE-26", + "text": "> **Ticket Issue Field Migrator** > **Configure**.\\n2. Specify the **Field Names** to migrate values from the ticket to the issue when fields are empty or undefined.\\n3. Click **Save** and **Install** to complete the setup.\\n4. Link an issue to a ticket to begin the migration of values from the ticket fields to the issue fields.\\n5. After the migration process is complete, you will receive a summary message in the snap-in **Discussion** tab, informing you of the number of fields processed,", "title": "Ticket issue field migrator | Automate | Snap-ins | DevRev" }, { - "id": "ART-13083_KNOWLEDGE_NODE-13", - "text": "field migrator](/docs/automations/ticket-issue-field-migrator)\\n * [Ticket Immutability](/docs/automations/ticket-immutability)\\n * [Ticket email notifier](/docs/automations/ticket-email-notifier)\\n * [Task tracker](/docs/automations/task-tracker)\\n * [Ticket Tagger](/docs/automations/ticket-tagger)\\n * [Tracxn sync](/docs/automations/tracxn-sync)\\n * [User group validator](/docs/automations/user-group-validator)\\n *", - "title": "| Automate | Snap-ins | DevRev" + "id": "ART-1961_KNOWLEDGE_NODE-37", + "text": "\\n{{Ticket\\xc2\\xa0Created\\xc2\\xa0>\\xc2\\xa0Output\\xc2\\xa0>\\xc2\\xa0Reported\\xc2\\xa0By\\xc2\\xa0>\\xc2\\xa0Rev\\xc2\\xa0Org\\xc2\\xa0>\\xc2\\xa0Display\\xc2\\xa0Name}}.\\xe2\\x80\\x9d\\n\\n\\n\\nDelay\\n\\n\\n\\nDuration: 2 minutes\\n\\n\\n\\nIf-else\\n\\n\\n\\nAttribute:\\xc2\\xa0Ticket\\xc2\\xa0Created/Output\\xc2\\xa0>\\xc2\\xa0Applies\\xc2\\xa0to\\xc2\\xa0part\\xc2\\xa0>\\xc2\\xa0Display\\xc2\\xa0ID \\nOperator: Equals \\nOperand: CAPL-18\\n\\n\\n\\nTicket \\ncreated\\n\\n\\n\\nEnd\\n```\\n\\n[### Workflow action", + "title": "Workflows | Computer by DevRev | DevRev" }, { - "id": "ART-2874_KNOWLEDGE_NODE-26", - "text": "> **Ticket Issue Field Migrator** > **Configure**.\\n2. Specify the **Field Names** to migrate values from the ticket to the issue when fields are empty or undefined.\\n3. Click **Save** and **Install** to complete the setup.\\n4. Link an issue to a ticket to begin the migration of values from the ticket fields to the issue fields.\\n5. After the migration process is complete, you will receive a summary message in the snap-in **Discussion** tab, informing you of the number of fields processed,", + "id": "ART-2874_KNOWLEDGE_NODE-24", + "text": "[Configuration](#configuration)\\n\\n1. [Documentation](/docs)\\n3. [Snap-ins](/docs/snapins)\\n[Automate](/docs/automate)\\n[Ticket issue field migrator](/docs/automations/ticket-issue-field-migrator)\\n\\nTicket issue field migrator\\n---------------------------\\n\\nThe Ticket issue field migration snap-in automates the transfer of custom field values from tickets to new linked issues in DevRev. It checks for empty or undefined fields and fills them with corresponding ticket values based on the field", "title": "Ticket issue field migrator | Automate | Snap-ins | DevRev" }, { - "id": "ART-2010_KNOWLEDGE_NODE-5", - "text": "ticket conversion](/docs/product/conversation-ticket)\\n + [Tickets](/docs/product/tickets)\\n + [Routing](/docs/product/routing)\\n + [Support best practices](/docs/product/support-bp)\\n + [Customer portal](/docs/product/support-portal)\\n + [Questions & answers](/docs/product/qa)\\n + [Knowledge Base](/docs/product/knowledge-base)\\n\\n - [Articles](/docs/product/articles)\\n - [Collections](/docs/product/collection)\\n + [Turing AI agent](/docs/product/conversational-bot)\\n\\n - [Best", - "title": "Bulk work item uploader | Automate | Snap-ins | DevRev" + "id": "ART-2048_KNOWLEDGE_NODE-30", + "text": "as necessary.\\n\\n If you want ClickUp tasks to become tickets rather than issues, map the task object to Works.Issue.\\n\\n While DevRev attempts to automatically map fields, you may be prompted to manually map indicated fields.\\n\\nThe duration of the import depends on the size of the ClickUp workspace and the\\ndata being imported. It can take seconds for a workspace with only a few dozen\\ntasks to a few hours for a workspace with tens of thousands of\\nitems with many attachments. DevRev", + "title": "ClickUp AirSync | AirSync | Snap-ins | DevRev" }, { - "id": "ART-4185_KNOWLEDGE_NODE-15", - "text": "[Custom field migration](/docs/automations/custom-field-migration)\\n - [Slack scraper](/docs/automations/slack-scraper)\\n - [Slack Broadcaster](/docs/automations/slack-broadcaster)\\n - [Reported by enricher](/docs/automations/ticket-reported-by)\\n - [Ticket approval workflow](/docs/automations/ticket-approval-workflow)\\n - [Ticket linked issues comment sync](/docs/automations/ticket-linked-issues-comment-sync)\\n - [Slack message agent](/docs/automations/slack-message-agent)\\n", - "title": "Ticket approval workflow | Automate | Snap-ins | DevRev" + "id": "ART-16803_KNOWLEDGE_NODE-26", + "text": "Tickets\\n* Meetings\\n* Objects linked to issues\\n* Users\\n\\nTo configure a workspace object loop:\\n\\n1. On the **workflow canvas**, add an action step named **Loop for [Object]**, where [Object] is the entity you want to iterate over.\\n2. Apply **filter conditions** to refine the set of objects included in the loop and perform operations on them.\\n\\nAll **actions** inside the loop execute once per object that satisfies the filter conditions.\\n\\n### For Each\\n\\nThe **For Each** loop iterates", + "title": "Workflow nodes | Workflows | Computer by DevRev | DevRev" }, { - "id": "ART-2874_KNOWLEDGE_NODE-10", - "text": "data](/docs/automations/bulk-delete)\\n - [Bulk work item uploader](/docs/automations/bulk-upload)\\n - [Commands surface expander](/docs/automations/commands-surface-expander)\\n - [Convergence](/docs/automations/converge)\\n - [Conversation reminder](/docs/automations/conversation-reminder)\\n - [CSAT on conversation](/docs/automations/csat-conv)\\n - [CSAT on ticket](/docs/automations/csat-tickets)\\n - [CSV work item uploader](/docs/automations/csv-work-item-uploader)\\n -", - "title": "Ticket issue field migrator | Automate | Snap-ins | DevRev" + "id": "ART-3107_KNOWLEDGE_NODE-25", + "text": "specific users (customer users).\\n* Ignores tickets created by other user types.\\n* Allows multiple tags to be assigned based on predefined rules.\\n* Can be triggered via commands or automatically when tickets are created.\\n\\nConfiguration\\n-------------\\n\\nFollow these steps to set up the Ticket Tagger:\\n\\n1. Go to **Snap-ins** > **Ticket Tagger** > **Configure**.\\n2. Fill in the configuration settings.\\n\\n * **Search for Tags**: Select the tags to check for on the contact or\\n account.", + "title": "Ticket Tagger | Automate | Snap-ins | DevRev" }, { - "id": "ART-2874_KNOWLEDGE_NODE-14", - "text": "Immutability](/docs/automations/ticket-immutability)\\n - [Ticket email notifier](/docs/automations/ticket-email-notifier)\\n - [Task tracker](/docs/automations/task-tracker)\\n - [Ticket Tagger](/docs/automations/ticket-tagger)\\n - [Tracxn sync](/docs/automations/tracxn-sync)\\n - [User group validator](/docs/automations/user-group-validator)\\n - [Work duration](/docs/automations/work-duration)\\n - [Operational SLA Metrics](/docs/automations/operational-sla-metrics)\\n -", - "title": "Ticket issue field migrator | Automate | Snap-ins | DevRev" + "id": "ART-15602_KNOWLEDGE_NODE-28", + "text": "by a Freshdesk account administrator.\\n\\n1. Once the connection is established, click the **AirSync** button. Select the Freshdesk account you want to import historical tickets from, and specify the DevRev part where the imported work should reside. This initiates a bulk ticket import.\\n2. DevRev automatically attempts to map fields from Freshdesk to their corresponding fields in DevRev. You may be prompted to manually map certain fields if automatic mapping is not possible.\\n\\nPost import", + "title": "Freshdesk historical ticket import | AirSync | Snap-ins | DevRev" }, { - "id": "ART-2874_KNOWLEDGE_NODE-27", - "text": "updated, and not updated. If the fields specified in the configuration are not found, a notification will be provided in the **Discussion** tab.\\n\\n[PreviousTicket age in engineering](/docs/automations/ticket-age-in-engineering)[NextTicket Immutability](/docs/automations/ticket-immutability)\\n\\n#### On this page\\n\\n* [Ticket issue field migrator](#ticket-issue-field-migrator)\\n* [Installation](#installation)\\n* [Configuration](#configuration)\\n\\n[Enterprise grade security to protect customer", - "title": "Ticket issue field migrator | Automate | Snap-ins | DevRev" + "id": "ART-13083_KNOWLEDGE_NODE-13", + "text": "field migrator](/docs/automations/ticket-issue-field-migrator)\\n * [Ticket Immutability](/docs/automations/ticket-immutability)\\n * [Ticket email notifier](/docs/automations/ticket-email-notifier)\\n * [Task tracker](/docs/automations/task-tracker)\\n * [Ticket Tagger](/docs/automations/ticket-tagger)\\n * [Tracxn sync](/docs/automations/tracxn-sync)\\n * [User group validator](/docs/automations/user-group-validator)\\n *", + "title": "| Automate | Snap-ins | DevRev" + }, + { + "id": "ART-8442_KNOWLEDGE_NODE-13", + "text": "field migrator](/docs/automations/ticket-issue-field-migrator)\\n * [Ticket Immutability](/docs/automations/ticket-immutability)\\n * [Ticket email notifier](/docs/automations/ticket-email-notifier)\\n * [Task tracker](/docs/automations/task-tracker)\\n * [Ticket Tagger](/docs/automations/ticket-tagger)\\n * [Tracxn sync](/docs/automations/tracxn-sync)\\n * [User group validator](/docs/automations/user-group-validator)\\n *", + "title": "January 2025 | Changelog | DevRev" } ] }, @@ -2972,9 +2972,14 @@ "query": "configure contact to open ticket in different workspace", "retrievals": [ { - "id": "ART-1979_KNOWLEDGE_NODE-55", - "text": "centralized in one location. This ticket not only retains the most comprehensive data but also acts as the focal point for tracking the progress of the customer's issue.\\n\\n### Merging guidelines\\n\\nTo ensure consistency and accuracy in the merging process, apply these guidelines when determining eligible tickets for merging:\\n\\n* Same workspace: All selected tickets must belong to the same customer workspace or have no workspace.\\n* Matching reporters: All selected tickets must have the same", - "title": "Tickets | Computer for Support Teams | DevRev" + "id": "ART-2874_KNOWLEDGE_NODE-25", + "text": "mappings specified in the configuration input. The process features robust error handling, detailed logging, and appends a summary comment to the timeline for easy update tracking.\\n\\nInstallation\\n------------\\n\\n1. Install the **Ticket Issue Field Migrator** snap-in from the DevRev marketplace.\\n2. Select the workspace where you want to install the snap-in, confirm your selection, and click **Deploy snap-in**.\\n\\nConfiguration\\n-------------\\n\\n1. In DevRev, go to **Settings** > **Snap-ins**", + "title": "Ticket issue field migrator | Automate | Snap-ins | DevRev" + }, + { + "id": "ART-1957_KNOWLEDGE_NODE-27", + "text": "[Issues](./issues#attributes)\\n* [Tickets](./tickets#attributes)\\n* [Opportunity](./grow#opportunity-attributes)\\n* [Account](./grow#account-attributes)\\n* [Contact](./grow#contact-attributes)\\n* [Parts](./parts#attributes)\\n\\n![]()\\n\\nAdding custom fields can be done by workspace admins only. Members of your organization can only view the custom fields and subtypes.\\n\\nTo get started with object customization, go to [**Settings** > **Object", + "title": "Object customization | Computer by DevRev | DevRev" }, { "id": "ART-1978_KNOWLEDGE_NODE-41", @@ -2982,44 +2987,39 @@ "title": "Customer portal | Computer for Support Teams | DevRev" }, { - "id": "ART-1979_KNOWLEDGE_NODE-38", - "text": "the top-right corner of your screen.\\n3. Add a title and description for your new ticket. You can also attach files related to the ticket in the description.\\n4. Select which part of the company/product this ticket is related to.\\n\\n ![]()\\n5. Enter other attributes for the ticket: change the assignee or accept the default; enter the severity; add any relevant tags to help employees identify any relevant traits of the ticket; select the workspace that the ticket pertains to.\\n6. If there are", - "title": "Tickets | Computer for Support Teams | DevRev" - }, - { - "id": "ART-6174_KNOWLEDGE_NODE-17", - "text": "* [Email snap-in configuration](/docs/integrations/email-config)\\n - [Exotel](/docs/integrations/exotel)\\n - [Slack](/docs/integrations/slack)\\n - [WhatsApp](/docs/integrations/whatsapp)\\n - [GitHub](/docs/integrations/github)\\n - [GitLab](/docs/integrations/gitlab)\\n - [Harness](/docs/integrations/harness)\\n - [Marker.io](/docs/integrations/marker-io)\\n - [Instabug](/docs/integrations/instabug)\\n - [Qase](/docs/integrations/qase)\\n - [Tracxn", - "title": "Conversation to ticket conversion | Conversations | Computer for Support Teams | DevRev" + "id": "ART-16264_KNOWLEDGE_NODE-28", + "text": "**Account** and **Reported By**. This provides a more streamlined approach to managing customer data.\\n* **Automatic workspace display:** When a ticket reporter is associated with a specific workspace within an account, adding that user to the **Reported By** field will automatically reveal three fields: **Account**, **Workspace**, and **Reported By**.\\n* **Dynamic user listing:**\\n\\n + Upon selection of an account, the **Reported By** list is filtered to show only users associated with that", + "title": "June 2025 | Changelog | DevRev" }, { - "id": "ART-1979_KNOWLEDGE_NODE-30", - "text": "the ticket was created.\\n* **Modified date**: The date the ticket was last modified.\\n* **Tags**: Tags are used to categorize tickets.\\n* **Customer workspace**: The workspace that the ticket pertains to. You can create a new account or workspace if it doesn't exist.\\n* **Target close date**: The date by which the issue is expected to be resolved.\\n* **Modified by**: The user who last modified the ticket.\\n* **Reported by**: Which customer is experiencing the issue. When a ticket is created", - "title": "Tickets | Computer for Support Teams | DevRev" + "id": "ART-2027_KNOWLEDGE_NODE-26", + "text": "configuration instructions, refer to [Email snap-in configuration](/docs/integrations/email-config).\\n\\nFor more information, refer to the [Email snap-in](/marketplace/email-with-tickets) on the DevRev marketplace.\\n\\nConversation and ticket creation for emails\\n-------------------------------------------\\n\\nWhen an email is received, DevRev checks if the sender is linked to your workspace and creates a conversation or ticket. If a sender is not recognized, DevRev creates a new user profile to", + "title": "Email | Integrate | Snap-ins | DevRev" }, { - "id": "ART-1979_KNOWLEDGE_NODE-62", - "text": "up ticket.\\n\\nThe below fields would be copied on the new follow up ticket from the archived/immutable ticket:\\n\\n* Part\\n* Channel\\n* Account\\n* Workspace\\n* Reported by\\n* Description\\n* Title\\n* Channel specific custom fields\\n* Subtype\\n\\nThe follow up trigger is added in the workflows and admins configure the changes required on new follow up ticket, for example, copying of any other fields.\\n\\nInternal Tickets\\n----------------\\n\\nInternal tickets allow your team to create and manage", - "title": "Tickets | Computer for Support Teams | DevRev" + "id": "ART-16803_KNOWLEDGE_NODE-26", + "text": "Tickets\\n* Meetings\\n* Objects linked to issues\\n* Users\\n\\nTo configure a workspace object loop:\\n\\n1. On the **workflow canvas**, add an action step named **Loop for [Object]**, where [Object] is the entity you want to iterate over.\\n2. Apply **filter conditions** to refine the set of objects included in the loop and perform operations on them.\\n\\nAll **actions** inside the loop execute once per object that satisfies the filter conditions.\\n\\n### For Each\\n\\nThe **For Each** loop iterates", + "title": "Workflow nodes | Workflows | Computer by DevRev | DevRev" }, { - "id": "ART-1947_KNOWLEDGE_NODE-28", - "text": "members from your own workspace and other members from the user\\'s workspace without starting a new thread or email chain. Because there can be many tickets attached to a single conversation, there is no need to start a new thread for new topics either.\\n\\nWe recommend closing the conversation whenever you feel the interaction has reached a natural end. Closing the conversation does not close the tickets and your external users are still able to see them in the widget.\\n\\nTickets\\n-------\\n\\nA", - "title": "Apps | Computer by DevRev | DevRev" + "id": "ART-15602_KNOWLEDGE_NODE-27", + "text": "snap-in\\n\\n1. Go to **Marketplace**, search for **Freshdesk (Historical Ticket Import)**, and click the **Add** button in the top right corner.\\n2. Once added, click the **Configure** button that appears in the top right corner. This opens the snap-in configuration modal.\\n3. Fill in the required fields in the configuration form and click **Submit**.\\n4. Create a new connection to your Freshdesk account, or select an existing one.\\n\\n![]()\\n\\nThe API token for the connection must be generated", + "title": "Freshdesk historical ticket import | AirSync | Snap-ins | DevRev" }, { - "id": "ART-2002_KNOWLEDGE_NODE-25", - "text": "about the customer initiating the conversation. Similarly, tickets on DevRev can capture who the ticket was reported by (or reported for).\\n\\nConcepts\\n--------\\n\\nCustomer identity in DevRev includes the following important constructs:\\n\\n* **External User/contact**: Your end user or customer or users associated with organization Accounts or Workspaces.\\n* **Account/workspace**: Any logical grouping that an external user is part of. It could represent a customer account for your B2B product", - "title": "Contacts | Computer for Growth Teams | DevRev" + "id": "ART-1979_KNOWLEDGE_NODE-26", + "text": "associated with a part (product or service) and can come from both internal and external users. Tickets are also used to communicate progress to the user or other impacted party.\\n\\nThere may be cases where mass communications (broadcast) are necessary in the event of lots of impacted or related parties (such as service status updates). In this scenario, the ticket would be used to broadcast and handle communications among multiple parties, including across multiple workspaces. Broadcast can", + "title": "Tickets | Computer for Support Teams | DevRev" }, { - "id": "ART-1981_KNOWLEDGE_NODE-30", - "text": "conversation of which you are not the owner, let the owner know to respond. It's beneficial to retain the same point of contact for the duration of the conversation unless the owner refers some another user.\\n* If the conversation has a customer org that's unidentified or is new, add yourself (the customer experience engineer) as the owner of the ticket. Try to find the appropriate owner for the customer org and update the customer record accordingly.\\n* Change the stage of the conversation to", - "title": "Support best practices | Computer for Support Teams | DevRev" + "id": "ART-12391_KNOWLEDGE_NODE-27", + "text": "workflow.\\n\\nNow, your workflow runs whenever a conversation or a ticket gets created and it\\nassigns it to an AI agent, which handles the conversation. No brittle rules.\\n\\nFind below a detailed explanation of all the fields needed to configure in the\\n\"Talk to Agent\" Step\\n\\n| Parameter | Type | Description |\\n| --- | --- | --- |\\n| agent | String | ID of the AI agent to use. Use the dropdown to select one. |\\n| object | String | ID of the conversation or ticket where the agent operate.s |\\n|", + "title": "Conversational workflows | Workflows | Computer by DevRev | DevRev" }, { - "id": "ART-1976_KNOWLEDGE_NODE-25", - "text": "and effective resolution. Users can design workflows tailored to various scenarios; the example below illustrates a basic routing use case.\\n\\n| NODE | ACTIVITY |\\n| --- | --- |\\n| Trigger | Ticket created |\\n| Action | Pick user by group |\\n| Action | Update ticket |\\n| | ID: Ticket created > Output > ID |\\n| | Group > Output > ID |\\n| | Owned by > Set: Pick user > Output > User |\\n\\nOrgs can set up pull-based routing by updating the group instead of the user ID in the workflow illustrated", - "title": "Routing | Computer for Support Teams | DevRev" + "id": "ART-2040_KNOWLEDGE_NODE-30", + "text": "established, select the Zendesk workspace you want to import and specify the DevRev part where the imported tickets should be created. This initiates a bulk import of the selected workspace.\\n4. DevRev makes an effort to automatically map the fields from Zendesk to corresponding fields in DevRev. However, you may be prompted to manually map certain fields if needed.\\n\\n![]()\\n\\nDevRev supports importing Zendesk organization custom fields. When importing organizations, AirSync will display", + "title": "Zendesk AirSync | AirSync | Snap-ins | DevRev" } ] }, @@ -3028,54 +3028,54 @@ "query": "link an agent with the search agent so that the search agent can ask the other agent", "retrievals": [ { - "id": "ART-2897_KNOWLEDGE_NODE-20", - "text": "agent is currently open or closed.\\n\\n[code]\\n\\n 1| window.plugSDK.isSearchAgentOpen \\n ---|---\\n[/code] \\n \\nThis returns `true` if the search agent is open and `false` if it is closed.\\n\\n## Prefill search query in search agent\\n\\nUse the `prefillSearchQuery` method to prefill a search query when opening and initializing the search agent.\\n\\n[code]\\n\\n 1| window.plugSDK.prefillSearchQuery(\"search_query\"); \\n ---|---\\n[/code] \\n \\n## Add session properties\\n\\nThe", - "title": "Methods \u2014 DevRev | Docs" + "id": "ART-15490_KNOWLEDGE_NODE-6", + "text": "Setup for React\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | |\\n```\\n\\nYou can modify the keydown event listener to bind it to other", + "title": "Install Plug search | DevRev | Docs" }, { - "id": "ART-15509_KNOWLEDGE_NODE-19", - "text": "status\\n-------------------------\\n\\nUse `isSearchAgentOpen` to determine whether the search agent is currently open or closed.\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | window.plugSDK.isSearchAgentOpen |\\n```\\n\\nThis returns `true` if the search agent is open and `false` if it is closed.\\n\\nPrefill search query in search agent\\n------------------------------------\\n\\nUse the `prefillSearchQuery` method to prefill a search query when opening and initializing the search agent.\\n\\n```\\n| | |\\n| ---", - "title": "Methods | DevRev | Docs" + "id": "ART-2665_KNOWLEDGE_NODE-31", + "text": "interactions occurring within the chat widget and search agent should be captured or not. | True |\\n| sessionDetails.sessionId | Field to pass session ID of the previous session to link. | null |\\n| sessionDetails.tabId | Field to pass the tab ID of the previous session to link. | null |\\n| maskTextFn | An option to customize the logic for masking sensitive text during session recording. This function accepts a callback that receives the text content and allows you to define how the text should", + "title": "Session recording options | Session analytics | Computer for Your Customers | DevRev" }, { - "id": "ART-1466_KNOWLEDGE_NODE-27", - "text": "Toggle search agent.\\n\\nThe toggleSearchAgent method allows you to control the visibility of the search agent.\\n\\nIf no input is provided, the method toggles the search bar: opening it if it\\xe2\\x80\\x99s closed, and closing it if it\\xe2\\x80\\x99s open.\\n\\n1 window. plugSDK. toggleSearchAgent ( true ) ; Prefill search query in search agent.\\n\\nUse the prefillSearchQuery method to prefill a search query when opening and initializing the search agent.\\n\\n1 window. plugSDK. prefillSearchQuery ( \"", - "title": "Methods \u2014 DevRev | Docs" + "id": "ART-1591_KNOWLEDGE_NODE-113", + "text": "api.devrev.ai / dev-users.identities.link\\nLinks an external/secondary identity to the Dev user.\\nRequest.\\n\\nThis endpoint expects an object.\\ndev_user string Required\\nThe ID of the Dev user to link the external identity to.\\nid string Required\\nUnique ID of the Dev user in the external source.\\nissuer string Required\\nIssuer of the external identity of the Dev user.\\ndisplay_name string Optional\\nDisplay name of the Dev user in the external source.\\nResponse.\\n\\nThis endpoint returns an", + "title": "Create \u2014 DevRev | Docs" }, { - "id": "ART-1466_KNOWLEDGE_NODE-26", - "text": "agent.\\n\\nCalling the initSearchAgent() method sets up the PLuG search agent on your website. This initialization is required before performing any other actions with the PLuG widget SDK.\\n\\n1 useEffect ( () => { 2 window. plugSDK. init ( { 3 app_id : \\' \\' , 4 disable_plug_chat_window : true , 5 } ) ; 6 7 window. plugSDK. onEvent ( ( payload ) => { 8 if ( payload. type === \\' ON_PLUG_WIDGET_READY \\' ) { 9 window. plugSDK. initSearchAgent () ; 10 } 11 } ) ; 12 } , []) ;", - "title": "Methods \u2014 DevRev | Docs" + "id": "ART-1590_KNOWLEDGE_NODE-113", + "text": "api.devrev.ai / dev-users.identities.link\\nLinks an external/secondary identity to the Dev user.\\nRequest.\\n\\nThis endpoint expects an object.\\ndev_user string Required\\nThe ID of the Dev user to link the external identity to.\\nid string Required\\nUnique ID of the Dev user in the external source.\\nissuer string Required\\nIssuer of the external identity of the Dev user.\\ndisplay_name string Optional\\nDisplay name of the Dev user in the external source.\\nResponse.\\n\\nThis endpoint returns an", + "title": "List \u2014 DevRev | Docs" }, { - "id": "ART-2897_KNOWLEDGE_NODE-19", - "text": "10| } \\n 11| }); \\n 12| }, []);\\n[/code] \\n \\n## Toggle search agent\\n\\nThe `toggleSearchAgent` method allows you to control the visibility of the search agent.\\n\\nIf no input is provided, the method toggles the search bar: opening it if it\\xe2\\x80\\x99s closed, and closing it if it\\xe2\\x80\\x99s open.\\n\\n[code]\\n\\n 1| window.plugSDK.toggleSearchAgent(true); \\n ---|---\\n[/code] \\n \\n## Check Search Agent status\\n\\nUse `isSearchAgentOpen` to determine whether the search", - "title": "Methods \u2014 DevRev | Docs" + "id": "ART-1832_KNOWLEDGE_NODE-113", + "text": "api.devrev.ai / dev-users.identities.link\\nLinks an external/secondary identity to the Dev user.\\nRequest.\\n\\nThis endpoint expects an object.\\ndev_user string Required\\nThe ID of the Dev user to link the external identity to.\\nid string Required\\nUnique ID of the Dev user in the external source.\\nissuer string Required\\nIssuer of the external identity of the Dev user.\\ndisplay_name string Optional\\nDisplay name of the Dev user in the external source.\\nResponse.\\n\\nThis endpoint returns an", + "title": "Create \u2014 DevRev | Docs" }, { - "id": "ART-15509_KNOWLEDGE_NODE-18", - "text": "window.plugSDK.initSearchAgent(); |\\n| 10 | } |\\n| 11 | }); |\\n| 12 | }, []); |\\n```\\n\\nToggle search agent\\n-------------------\\n\\nThe `toggleSearchAgent` method allows you to control the visibility of the search agent.\\n\\nIf no input is provided, the method toggles the search bar: opening it if it\\xe2\\x80\\x99s closed, and closing it if it\\xe2\\x80\\x99s open.\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | window.plugSDK.toggleSearchAgent(true); |\\n```\\n\\nCheck Search Agent", - "title": "Methods | DevRev | Docs" + "id": "ART-1579_KNOWLEDGE_NODE-113", + "text": "api.devrev.ai / dev-users.identities.link\\nLinks an external/secondary identity to the Dev user.\\nRequest.\\n\\nThis endpoint expects an object.\\ndev_user string Required\\nThe ID of the Dev user to link the external identity to.\\nid string Required\\nUnique ID of the Dev user in the external source.\\nissuer string Required\\nIssuer of the external identity of the Dev user.\\ndisplay_name string Optional\\nDisplay name of the Dev user in the external source.\\nResponse.\\n\\nThis endpoint returns an", + "title": "List Post \u2014 DevRev | Docs" }, { - "id": "ART-15490_KNOWLEDGE_NODE-5", - "text": "shared any information.\\n\\nAfter integrating the Plug widget, you can personalize and contextualize customer engagement. Learn how to [identify your customers](/sdks/web/user-identity) and update their information.\\n\\nBind a hotkey to toggle search agent\\n------------------------------------\\n\\nYou can bind the `toggleSearchAgent` method to a hotkey, such as `Cmd + K` (or `Ctrl + K` for Windows), to toggle the search agent. Here\\xe2\\x80\\x99s an example implementation:\\n\\n###### Setup\\n\\n######", - "title": "Install Plug search | DevRev | Docs" + "id": "ART-1806_KNOWLEDGE_NODE-113", + "text": "api.devrev.ai / dev-users.identities.link\\nLinks an external/secondary identity to the Dev user.\\nRequest.\\n\\nThis endpoint expects an object.\\ndev_user string Required\\nThe ID of the Dev user to link the external identity to.\\nid string Required\\nUnique ID of the Dev user in the external source.\\nissuer string Required\\nIssuer of the external identity of the Dev user.\\ndisplay_name string Optional\\nDisplay name of the Dev user in the external source.\\nResponse.\\n\\nThis endpoint returns an", + "title": "Self Post \u2014 DevRev | Docs" }, { - "id": "ART-15509_KNOWLEDGE_NODE-1", - "text": "conversation](/sdks/web/methods#start-conversation)\\n* [Shutdown](/sdks/web/methods#shutdown)\\n* [Initialize the search agent](/sdks/web/methods#initialize-the-search-agent)\\n* [Toggle search agent](/sdks/web/methods#toggle-search-agent)\\n* [Check Search Agent status](/sdks/web/methods#check-search-agent-status)\\n* [Prefill search query in search agent](/sdks/web/methods#prefill-search-query-in-search-agent)\\n* [Add session properties](/sdks/web/methods#add-session-properties)\\n* [Get session", - "title": "Methods | DevRev | Docs" + "id": "ART-1819_KNOWLEDGE_NODE-113", + "text": "api.devrev.ai / dev-users.identities.link\\nLinks an external/secondary identity to the Dev user.\\nRequest.\\n\\nThis endpoint expects an object.\\ndev_user string Required\\nThe ID of the Dev user to link the external identity to.\\nid string Required\\nUnique ID of the Dev user in the external source.\\nissuer string Required\\nIssuer of the external identity of the Dev user.\\ndisplay_name string Optional\\nDisplay name of the Dev user in the external source.\\nResponse.\\n\\nThis endpoint returns an", + "title": "Sla Trackers Get \u2014 DevRev | Docs" }, { - "id": "ART-2894_KNOWLEDGE_NODE-4", - "text": "2| window.plugSDK.init({ \\n 3| app_id: \\'\\', \\n 4| disable_plug_chat_window: true, \\n 5| }); \\n 6| \\n 7| window.plugSDK.onEvent((payload) => { \\n 8| if (payload.type === \\'ON_PLUG_WIDGET_READY\\') { \\n 9| window.plugSDK.initSearchAgent(); \\n 10| } \\n 11| }); \\n 12| \\n[/code] \\n \\nTo toggle `searchAgent`, call the following method on any event required:\\n\\n[code]\\n\\n", - "title": "Install PLuG search \u2014 DevRev | Docs" + "id": "ART-1838_KNOWLEDGE_NODE-113", + "text": "api.devrev.ai / dev-users.identities.link\\nLinks an external/secondary identity to the Dev user.\\nRequest.\\n\\nThis endpoint expects an object.\\ndev_user string Required\\nThe ID of the Dev user to link the external identity to.\\nid string Required\\nUnique ID of the Dev user in the external source.\\nissuer string Required\\nIssuer of the external identity of the Dev user.\\ndisplay_name string Optional\\nDisplay name of the Dev user in the external source.\\nResponse.\\n\\nThis endpoint returns an", + "title": "List Post \u2014 DevRev | Docs" }, { - "id": "ART-4090_KNOWLEDGE_NODE-13", - "text": "[Subprocessors](https://devrev.ai/security/sub-processors)\\n * [Cookie Policy](https://devrev.ai/legal/cookie-policy)\\n * [Privacy Policy](https://devrev.ai/legal/privacy-policy)\\n * [Terms of Service](https://devrev.ai/legal/terms-of-service)\\n\\nLearn\\n\\n * [What are AI Agents?](https://devrev.ai/what-are-ai-agents)\\n * [What is Agentic AI?](https://devrev.ai/what-is-agentic-ai)\\n * [What is Enterprise Search?](https://devrev.ai/what-is-enterprise-search)\\n * [What is Conversational", - "title": "Create Link \u2014 DevRev | Docs" + "id": "ART-1633_KNOWLEDGE_NODE-113", + "text": "api.devrev.ai / dev-users.identities.link\\nLinks an external/secondary identity to the Dev user.\\nRequest.\\n\\nThis endpoint expects an object.\\ndev_user string Required\\nThe ID of the Dev user to link the external identity to.\\nid string Required\\nUnique ID of the Dev user in the external source.\\nissuer string Required\\nIssuer of the external identity of the Dev user.\\ndisplay_name string Optional\\nDisplay name of the Dev user in the external source.\\nResponse.\\n\\nThis endpoint returns an", + "title": "List \u2014 DevRev | Docs" } ] }, @@ -3088,50 +3088,50 @@ "text": "DevRev's left navigation is designed to provide a more customizable and intuitive navigation experience. This update introduces new sections for better organization, enhanced customization capabilities, and a dedicated **Explore** page for managing views, dashboards, and sprint boards.\\n\\nWhen existing users log in, a prompt appears to guide them in migrating to the new left navigation. Follow the on-screen instructions to complete the migration and begin customizing your experience.\\n\\n## Key", "title": "October 5: Left navigation | Changelog | DevRev" }, - { - "id": "ART-1944_KNOWLEDGE_NODE-0", - "text": "b\"Product Platform Solutions Marketplace Company Resources Pricing\\n\\nLogin Book a demo\\nProduct Platform Solutions Marketplace Company Resources Pricing\\nLogin Book a demo\\nSearch CTRL + K\\n\\nIntroduction AgentOS platform\\n\\nCore concepts Apps Groups Parts & trails Vistas Vista Reports\\nTasks Updates Customer email notifications Roles Default privileges by group\\nAccess control Object customization Glossary Search People insights Workflow Templates Accessing DevRev External identity provider", - "title": "DevRev Documentation" - }, { "id": "ART-2666_KNOWLEDGE_NODE-26", - "text": "[Developer](https://developer.devrev.ai/)\\n * [DevRevU](/docs/DevRevU)\\n\\n * [Product demos](/docs/DevRevU/demos)\\n\\nOn this page\\n\\n * Key changes\\n * New navigation sections\\n * Explore the section for boards and views\\n * Search and filter options in Explore\\n * Pinning and unpinning views\\n * Recents section\\n\\n 1. [Documentation](/docs)\\n 2. 3. [Changelog](/docs/changelog)\\n 4. [October 5: Left navigation](/docs/product/left-navigation)\\n\\n# Left navigation\\n\\nThe updated", + "text": "[Developer](https://developer.devrev.ai/)\\n * [DevRevU](/docs/DevRevU)\\n\\n * [Product demos](/docs/DevRevU/demos)\\n\\nOn this page\\n\\n * Key changes\\n * New navigation sections\\n * Explore the section for boards and views\\n * Search and filter options in Explore\\n * Pinning and unpinning views\\n * Recents section\\n\\n 1. [Documentation](/docs)\\n 2. 3. [Changelog](/docs/changelog)\\n 4. [October 5: Left navigation](/docs/product/left-navigation)\\n\\n# Left navigation\\n\\nThe updated", "title": "October 5: Left navigation | Changelog | DevRev" }, { - "id": "ART-2666_KNOWLEDGE_NODE-0", - "text": "b\"[](/)\\n\\n * Product\\n * Platform\\n * Marketplace\\n * Company\\n * Resources\\n * Pricing\\n\\n __\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](/request-a-demo)\\n\\n[](/)\\n\\n __\\n\\nProduct __\\n\\nPlatform __\\n\\nMarketplace __\\n\\nCompany __\\n\\nResources __\\n\\nPricing __\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](/request-a-demo)\\n\\nSearch\\n\\n`CTRL` \\\\+ `K`\\n\\n * [Introduction](/docs)\\n * [AgentOS platform](/docs/intro)\\n\\n * [Core concepts](/docs/product/core)\\n *", - "title": "October 5: Left navigation | Changelog | DevRev" + "id": "ART-12475_KNOWLEDGE_NODE-1", + "text": ".\\n\\nProceed to integrate the DevRev PLuG SDK. For specific platform migration guides, refer to the following resources:\\n\\nAndroid SDK migration guide: Android Migration Guide\\n\\niOS SDK migration guide: iOS Migration Guide\\n\\nReact Native & Expo SDK migration guide: React Native Migration Guide\\n\\nCordova SDK migration guide: Cordova Migration Guide\\n\\nWeb SDK migration guide: Web Migration Guide\\n\\nOnce the integration is complete, you will be able to view sessions on the Session", + "title": "Migrating from UserExperior to DevRev" }, { - "id": "ART-12450_KNOWLEDGE_NODE-7", - "text": "page helpful?YesNo\\n\\n[FeaturesUp Next](/public/sdks/ios/features)\\n\\n[Built with](https://buildwithfern.com/?utm_campaign=buildWith&utm_medium=docs&utm_source=developer.devrev.ai)\\n\\n[Enterprise grade security to protect customer dataLearn more about it.](https://devrev.ai/blog/soc-compliance)\\n\\nProduct\\n\\n * [Build](https://devrev.ai/build)\\n * [Support](https://devrev.ai/support)\\n * [Search](https://devrev.ai/search)\\n * [PLuG - User", - "title": "Quickstart guide \u2014 DevRev | Docs" + "id": "ART-16570_KNOWLEDGE_NODE-8", + "text": "access\\n--------------------------------------------------------------\\n\\n**The Transformation Journey**\\n\\nThe shift from FAME\\'s previous fragmented information landscape to DevRev\\'s unified memory represented a fundamental change in how teams work. What once required navigating multiple platforms, piecing together incomplete information, and spending hours searching for answers became as simple as having a conversation.\\n\\nDevRev\\'s AirSync technology seamlessly ingested FAME\\'s existing", + "title": "FAME transforms information access with AI-powered enterprise search" }, { - "id": "ART-2666_KNOWLEDGE_NODE-28", - "text": "changes\\n\\n### New navigation sections\\n\\nThe updated left navigation includes the following sections:\\n\\n * **Work**\\n * **Product**\\n * **Customer**\\n * **People**\\n\\nThese new sections replace the former categories of **Build** , **Product** , **Support** , and **Grow** , offering a more personalized user experience. You can set defaults based on your primary application preferences and add custom views to these sections for easier access.\\n\\n### Explore the section for boards and", - "title": "October 5: Left navigation | Changelog | DevRev" + "id": "ART-2819_KNOWLEDGE_NODE-0", + "text": "b\"Exotel | Integrate | Snap-ins | DevRev\\n\\n* Computer\\n* Resources\\n* [Our Customers](/case-study)\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](/request-a-demo)\\n\\nComputer\\n\\nResources\\n\\n[Our Customers](/case-study)\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](/request-a-demo)\\n\\nSearch\\n\\n`CMD`\\xc2\\xa0+\\xc2\\xa0`K`\\n\\n* [Introduction](/docs)\\n* [Computer by DevRev](/docs/intro)\\n\\n + [Core concepts](/docs/product/core)\\n + [Apps](/docs/product/apps)\\n +", + "title": "Exotel | Integrate | Snap-ins | DevRev" }, { - "id": "ART-15498_KNOWLEDGE_NODE-8", - "text": "helpful?\\n\\nYesNo\\n\\n[Previous](/sdks/web/migration)[#### Features\\n\\nNext](/sdks/android/features)[Built with](https://buildwithfern.com/?utm_campaign=buildWith&utm_medium=docs&utm_source=developer.devrev.ai)'", - "title": "Quickstart guide | DevRev | Docs" + "id": "ART-13079_KNOWLEDGE_NODE-9", + "text": "English).\\n * Result-oriented work style, ability to get things done and a learning mindset.\\n * An endless passion for challenging work that requires high energy, full engagement and a self-founded need for high performance.\\n\\n**Culture**\\n\\nThe foundation of DevRev is its culture -- our commitment to those who are hungry, humble, honest, and who act with heart. Our vision is to help build the earth\\xe2\\x80\\x99s most customer-centric companies. Our mission is to leverage design, data", + "title": "DevRev Careers | Applied AI Engineer - Support" }, { - "id": "ART-2662_KNOWLEDGE_NODE-1", - "text": "[Parts & trails](/docs/product/parts)\\n + [Vistas](/docs/product/vistas)\\n\\n - [Vista Reports](/docs/product/vista-reports)\\n - [Board view](/docs/product/board-view)\\n + [Tasks](/docs/product/tasks)\\n + [Updates](/docs/product/updates)\\n + [Customer email notifications](/docs/product/customer-emails)\\n + [Roles](/docs/product/roles)\\n\\n - [Default privileges by group](/docs/product/privs)\\n + [Access control](/docs/product/access-control)\\n + [Object", - "title": "DevRev Documentation" + "id": "ART-2031_KNOWLEDGE_NODE-0", + "text": "b\"Harness | Integrate | Snap-ins | DevRev\\n\\n* Computer\\n* Resources\\n* [Our Customers](/case-study)\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](/request-a-demo)\\n\\nComputer\\n\\nResources\\n\\n[Our Customers](/case-study)\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](/request-a-demo)\\n\\nSearch\\n\\n`CTRL`\\xc2\\xa0+\\xc2\\xa0`K`\\n\\n* [Introduction](/docs)\\n* [Computer by DevRev](/docs/intro)\\n\\n + [Core concepts](/docs/product/core)\\n + [Apps](/docs/product/apps)\\n +", + "title": "Harness | Integrate | Snap-ins | DevRev" }, { "id": "ART-2662_KNOWLEDGE_NODE-0", - "text": "b'DevRev Documentation\\n\\n* Computer\\n* Resources\\n* [Our Customers](/case-study)\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](/request-a-demo)\\n\\nComputer\\n\\nResources\\n\\n[Our Customers](/case-study)\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](/request-a-demo)\\n\\nSearch\\n\\n`CTRL`\\xc2\\xa0+\\xc2\\xa0`K`\\n\\n* [Introduction](/docs)\\n* [Computer by DevRev](/docs/intro)\\n\\n + [Core concepts](/docs/product/core)\\n + [Apps](/docs/product/apps)\\n + [Groups](/docs/product/groups)\\n +", + "text": "b'DevRev Documentation\\n\\n* Computer\\n* Resources\\n* [Our Customers](/case-study)\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](/request-a-demo)\\n\\nComputer\\n\\nResources\\n\\n[Our Customers](/case-study)\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](/request-a-demo)\\n\\nSearch\\n\\n`CTRL`\\xc2\\xa0+\\xc2\\xa0`K`\\n\\n* [Introduction](/docs)\\n* [Computer by DevRev](/docs/intro)\\n\\n + [Core concepts](/docs/product/core)\\n + [Apps](/docs/product/apps)\\n + [Groups](/docs/product/groups)\\n +", "title": "DevRev Documentation" }, { - "id": "ART-12461_KNOWLEDGE_NODE-0", - "text": "b'[](/public/sdks/cordova/quickstart)\\n\\nPublic\\n\\n[](https://devrev.ai)\\n\\n * Product\\n * Platform\\n * Solutions\\n * Marketplace\\n * Company\\n * Resources\\n * [Pricing](https://devrev.ai/pricing)\\n\\n __\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](https://devrev.ai/request-a-demo)\\n\\n[](https://devrev.ai)\\n\\n __\\n\\nProduct __\\n\\nPlatform __\\n\\nSolutions __\\n\\nMarketplace __\\n\\nCompany __\\n\\nResources", - "title": "Quickstart guide \u2014 DevRev | Docs" + "id": "ART-2035_KNOWLEDGE_NODE-0", + "text": "b\"Slack | Integrate | Snap-ins | DevRev\\n\\n* Computer\\n* Resources\\n* [Our Customers](/case-study)\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](/request-a-demo)\\n\\nComputer\\n\\nResources\\n\\n[Our Customers](/case-study)\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](/request-a-demo)\\n\\nSearch\\n\\n`CTRL`\\xc2\\xa0+\\xc2\\xa0`K`\\n\\n* [Introduction](/docs)\\n* [Computer by DevRev](/docs/intro)\\n\\n + [Core concepts](/docs/product/core)\\n + [Apps](/docs/product/apps)\\n +", + "title": "Slack | Integrate | Snap-ins | DevRev" + }, + { + "id": "ART-2043_KNOWLEDGE_NODE-0", + "text": "b'Glean | Integrate | Snap-ins | DevRev\\n\\n* Computer\\n* Resources\\n* [Our Customers](/case-study)\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](/request-a-demo)\\n\\nComputer\\n\\nResources\\n\\n[Our Customers](/case-study)\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](/request-a-demo)\\n\\nSearch\\n\\n`CTRL`\\xc2\\xa0+\\xc2\\xa0`K`\\n\\n* [Introduction](/docs)\\n* [Computer by DevRev](/docs/intro)\\n\\n + [Core concepts](/docs/product/core)\\n + [Apps](/docs/product/apps)\\n +", + "title": "Glean | Integrate | Snap-ins | DevRev" } ] }, @@ -3140,54 +3140,54 @@ "query": "common causes of Bad_Request error in DevRev", "retrievals": [ { - "id": "ART-1364_KNOWLEDGE_NODE-3", - "text": "\\n`429`| `Too Many Requests`| The user is currently throttled due to exceeding their permitted rate limit. The `Retry-After` response header contains the number of seconds before the user should retry. \\n`500`| `Internal Server Error`| An internal error was encountered in the handling of the request which couldn\\xe2\\x80\\x99t be processed to completion. DevRev is automatically alerted to any occurrence of this error. The user should retry after a short delay and contact DevRev support if the", - "title": "Errors \u2014 DevRev | Docs" + "id": "ART-3896_KNOWLEDGE_NODE-3", + "text": "Errors\\n\\n400\\n\\nBad Request Error\\n\\n401\\n\\nUnauthorized Error\\n\\n403\\n\\nForbidden Error\\n\\n429\\n\\nToo Many Requests Error\\n\\n500\\n\\nInternal Server Error\\n\\n503\\n\\nService Unavailable Error\\n\\nPOST\\n\\n/stage-diagrams.create\\n\\n[code]\\n\\n $| curl -X POST https://api.devrev.ai/stage-diagrams.create \\\\ \\n ---|--- \\n >| -H \"Authorization: Bearer \" \\\\ \\n >| -H \"Content-Type: application/json\" \\\\ \\n >| -d \\'{ \\n >| \"leaf_type\": \"foo\", \\n >|", + "title": "Create Stage Diagram (Beta) \u2014 DevRev | Docs" }, { - "id": "ART-15376_KNOWLEDGE_NODE-3", - "text": "request to merge Dev users.\\n\\n### Errors\\n\\n400\\n\\nBad Request Error\\n\\n401\\n\\nUnauthorized Error\\n\\n403\\n\\nForbidden Error\\n\\n404\\n\\nNot Found Error\\n\\n429\\n\\nToo Many Requests Error\\n\\n500\\n\\nInternal Server Error\\n\\n503\\n\\nService Unavailable Error\\n\\nWas this page helpful?\\n\\nYesNo\\n\\n[Previous](/api-reference/dev-users/list-post)[#### Self Dev User\\n\\nNext](/api-reference/dev-users/self)[Built", - "title": "Merge Dev Users | DevRev | Docs" + "id": "ART-4098_KNOWLEDGE_NODE-1", + "text": "Request Error\\n\\n401\\n\\nUnauthorized Error\\n\\n403\\n\\nForbidden Error\\n\\n404\\n\\nNot Found Error\\n\\n429\\n\\nToo Many Requests Error\\n\\n500\\n\\nInternal Server Error\\n\\n503\\n\\nService Unavailable Error\\n\\nGET\\n\\n/rev-users.get\\n\\n[code]\\n\\n $| curl -G https://api.devrev.ai/rev-users.get \\\\ \\n ---|--- \\n >| -H \"Authorization: Bearer \" \\\\ \\n >| -d id=id\\n[/code] \\n \\nTry it\\n\\n200getExample\\n\\n[code]\\n\\n 1| { \\n ---|--- \\n 2| \"rev_user\": { \\n 3|", + "title": "Get Rev User \u2014 DevRev | Docs" }, { - "id": "ART-1204_KNOWLEDGE_NODE-9", - "text": "Error\\n\\n429\\n\\nToo Many Requests Error\\n\\n500\\n\\nInternal Server Error\\n\\n503\\n\\nService Unavailable Error\\n\\nWas this page helpful?\\n\\nYesNo\\n\\n[Previous](/api-reference/dev-users/get)[#### Link Dev Users Identities\\n\\nNext](/api-reference/dev-users/identities-link)[Built with](https://buildwithfern.com/?utm_campaign=buildWith&utm_medium=docs&utm_source=developer.devrev.ai)'", - "title": "Get Dev User (POST) | DevRev | Docs" + "id": "ART-12991_KNOWLEDGE_NODE-1", + "text": "Request Error\\n\\n401\\n\\nUnauthorized Error\\n\\n403\\n\\nForbidden Error\\n\\n404\\n\\nNot Found Error\\n\\n429\\n\\nToo Many Requests Error\\n\\n500\\n\\nInternal Server Error\\n\\n503\\n\\nService Unavailable Error\\n\\nPOST\\n\\n/dev-users.deactivate\\n\\n[code]\\n\\n $| curl -X POST https://api.devrev.ai/dev-users.deactivate \\\\ \\n ---|--- \\n >| -H \"Authorization: Bearer \" \\\\ \\n >| -H \"Content-Type: application/json\" \\\\ \\n >| -d \\'{ \\n >| \"id\": \"foo\" \\n >| }\\'\\n[/code]", + "title": "Deactivate Dev Users \u2014 DevRev | Docs" }, { - "id": "ART-15449_KNOWLEDGE_NODE-3", - "text": "Error\\n\\n429\\n\\nToo Many Requests Error\\n\\n500\\n\\nInternal Server Error\\n\\n503\\n\\nService Unavailable Error\\n\\nWas this page helpful?\\n\\nYesNo\\n\\n[Previous](/api-reference/rev-users/list-post)[#### Scan Rev Users\\n\\nNext](/api-reference/rev-users/scan)[Built with](https://buildwithfern.com/?utm_campaign=buildWith&utm_medium=docs&utm_source=developer.devrev.ai)'", - "title": "Merge Rev Users | DevRev | Docs" + "id": "ART-4097_KNOWLEDGE_NODE-1", + "text": "Error\\n\\n401\\n\\nUnauthorized Error\\n\\n403\\n\\nForbidden Error\\n\\n404\\n\\nNot Found Error\\n\\n429\\n\\nToo Many Requests Error\\n\\n500\\n\\nInternal Server Error\\n\\n503\\n\\nService Unavailable Error\\n\\nPOST\\n\\n/rev-users.delete\\n\\n[code]\\n\\n $| curl -X POST https://api.devrev.ai/rev-users.delete \\\\ \\n ---|--- \\n >| -H \"Authorization: Bearer \" \\\\ \\n >| -H \"Content-Type: application/json\" \\\\ \\n >| -d \\'{ \\n >| \"id\": \"foo\" \\n >| }\\'\\n[/code] \\n \\nTry", + "title": "Delete Rev User \u2014 DevRev | Docs" }, { - "id": "ART-1364_KNOWLEDGE_NODE-2", - "text": "{\"message\":\"route not found\"}\\n[/code] \\n \\nStatus Code| Status| Description \\n---|---|--- \\n`400`| `Bad Request`| The request was malformed or contained invalid arguments. \\n`401`| `Unauthorized`| The user attempted to access an endpoint that requires authentication and no credentials were provided or their validation failed. \\n`403`| `Forbidden`| The user isn\\xe2\\x80\\x99t authorized to perform the requested action. \\n`404`| `Not Found`| The requested endpoint doesn\\xe2\\x80\\x99t exist.", - "title": "Errors \u2014 DevRev | Docs" + "id": "ART-1174_KNOWLEDGE_NODE-3", + "text": "to perform the requested action. |\\n| `404` | `Not Found` | The requested endpoint doesn\\xe2\\x80\\x99t exist. |\\n| `429` | `Too Many Requests` | The user is currently throttled due to exceeding their permitted rate limit. The `Retry-After` response header contains the number of seconds before the user should retry. |\\n| `500` | `Internal Server Error` | An internal error was encountered in the handling of the request which couldn\\xe2\\x80\\x99t be processed to completion. DevRev is automatically", + "title": "Errors | DevRev | Docs" }, { - "id": "ART-15440_KNOWLEDGE_NODE-9", - "text": "Error\\n\\n409\\n\\nConflict Error\\n\\n429\\n\\nToo Many Requests Error\\n\\n500\\n\\nInternal Server Error\\n\\n503\\n\\nService Unavailable Error\\n\\nWas this page helpful?\\n\\nYesNo\\n\\n[Previous](/api-reference/rev-users/scan-post)[#### Create Service Account\\n\\nNext](/api-reference/service-accounts/create)[Built with](https://buildwithfern.com/?utm_campaign=buildWith&utm_medium=docs&utm_source=developer.devrev.ai)'", - "title": "Update Rev User | DevRev | Docs" + "id": "ART-1205_KNOWLEDGE_NODE-11", + "text": "Error\\n\\n403\\n\\nForbidden Error\\n\\n429\\n\\nToo Many Requests Error\\n\\n500\\n\\nInternal Server Error\\n\\n503\\n\\nService Unavailable Error\\n\\nWas this page helpful?\\n\\nYesNo\\n\\n[Previous](/api-reference/dev-users/identities-unlink)[#### List Dev Users (POST)\\n\\nNext](/api-reference/dev-users/list-post)[Built with](https://buildwithfern.com/?utm_campaign=buildWith&utm_medium=docs&utm_source=developer.devrev.ai)'", + "title": "List Dev Users | DevRev | Docs" }, { - "id": "ART-4097_KNOWLEDGE_NODE-1", - "text": "Error\\n\\n401\\n\\nUnauthorized Error\\n\\n403\\n\\nForbidden Error\\n\\n404\\n\\nNot Found Error\\n\\n429\\n\\nToo Many Requests Error\\n\\n500\\n\\nInternal Server Error\\n\\n503\\n\\nService Unavailable Error\\n\\nPOST\\n\\n/rev-users.delete\\n\\n[code]\\n\\n $| curl -X POST https://api.devrev.ai/rev-users.delete \\\\ \\n ---|--- \\n >| -H \"Authorization: Bearer \" \\\\ \\n >| -H \"Content-Type: application/json\" \\\\ \\n >| -d \\'{ \\n >| \"id\": \"foo\" \\n >| }\\'\\n[/code] \\n \\nTry", - "title": "Delete Rev User \u2014 DevRev | Docs" + "id": "ART-1364_KNOWLEDGE_NODE-3", + "text": "\\n`429`| `Too Many Requests`| The user is currently throttled due to exceeding their permitted rate limit. The `Retry-After` response header contains the number of seconds before the user should retry. \\n`500`| `Internal Server Error`| An internal error was encountered in the handling of the request which couldn\\xe2\\x80\\x99t be processed to completion. DevRev is automatically alerted to any occurrence of this error. The user should retry after a short delay and contact DevRev support if the", + "title": "Errors \u2014 DevRev | Docs" }, { - "id": "ART-1213_KNOWLEDGE_NODE-5", - "text": "properties\\n\\n### Errors\\n\\n400\\n\\nBad Request Error\\n\\n401\\n\\nUnauthorized Error\\n\\n403\\n\\nForbidden Error\\n\\n404\\n\\nNot Found Error\\n\\n429\\n\\nToo Many Requests Error\\n\\n500\\n\\nInternal Server Error\\n\\n503\\n\\nService Unavailable Error\\n\\nWas this page helpful?\\n\\nYesNo\\n\\n[Previous](/api-reference/rev-orgs/delete)[#### Get Rev Org (POST)\\n\\nNext](/api-reference/rev-orgs/get-post)[Built with](https://buildwithfern.com/?utm_campaign=buildWith&utm_medium=docs&utm_source=developer.devrev.ai)'", - "title": "Get Rev Org | DevRev | Docs" + "id": "ART-4061_KNOWLEDGE_NODE-3", + "text": "Error\\n\\n429\\n\\nToo Many Requests Error\\n\\n500\\n\\nInternal Server Error\\n\\n503\\n\\nService Unavailable Error\\n\\nPOST\\n\\n/dev-users.self.update\\n\\n[code]\\n\\n $| curl -X POST https://api.devrev.ai/dev-users.self.update \\\\ \\n ---|--- \\n >| -H \"Authorization: Bearer \" \\\\ \\n >| -H \"Content-Type: application/json\" \\\\ \\n >| -d \\'{}\\'\\n[/code] \\n \\nTry it\\n\\n200devUsersSelfUpdateExample\\n\\n[code]\\n\\n 1| { \\n ---|--- \\n 2| \"dev_user\": { \\n 3|", + "title": "Update Dev Users Self \u2014 DevRev | Docs" }, { - "id": "ART-15314_KNOWLEDGE_NODE-8", - "text": "Errors\\n\\n400\\n\\nBad Request Error\\n\\n401\\n\\nUnauthorized Error\\n\\n403\\n\\nForbidden Error\\n\\n404\\n\\nNot Found Error\\n\\n429\\n\\nToo Many Requests Error\\n\\n500\\n\\nInternal Server Error\\n\\n503\\n\\nService Unavailable Error\\n\\nWas this page helpful?\\n\\nYesNo\\n\\n[Previous](/api-reference/code-changes/update)[#### Get Command\\n\\nNext](/api-reference/commands/get)[Built with](https://buildwithfern.com/?utm_campaign=buildWith&utm_medium=docs&utm_source=developer.devrev.ai)'", - "title": "Create Command | DevRev | Docs" + "id": "ART-1174_KNOWLEDGE_NODE-0", + "text": "b'Errors | DevRev | Docs\\n\\n[![]()![]()](https://developer.devrev.ai/)\\n\\nPublic\\n\\nPublic\\n\\nSearch\\n\\n`/`\\n\\n[About](/about/for-developers)\\n\\nErrors\\n======\\n\\nCopy page\\n\\nDevRev\\xe2\\x80\\x99s APIs use standard HTTP status codes when responding to requests. On success, a `20X` status code is returned along with any response data, as indicated in the OpenAPI specification.\\n\\n| Status Code | Status | Description |\\n| --- | --- | --- |\\n| `200` | `OK` | The request succeeded and the result is", + "title": "Errors | DevRev | Docs" }, { - "id": "ART-1205_KNOWLEDGE_NODE-11", - "text": "Error\\n\\n403\\n\\nForbidden Error\\n\\n429\\n\\nToo Many Requests Error\\n\\n500\\n\\nInternal Server Error\\n\\n503\\n\\nService Unavailable Error\\n\\nWas this page helpful?\\n\\nYesNo\\n\\n[Previous](/api-reference/dev-users/identities-unlink)[#### List Dev Users (POST)\\n\\nNext](/api-reference/dev-users/list-post)[Built with](https://buildwithfern.com/?utm_campaign=buildWith&utm_medium=docs&utm_source=developer.devrev.ai)'", - "title": "List Dev Users | DevRev | Docs" + "id": "ART-1854_KNOWLEDGE_NODE-6", + "text": "retries is exhausted, the errored events are moved to a dead-letter queue (DLQ) for further handling.\\n\\n## Error interface\\n\\nThe DevRev SDK defines the `FunctionExecutionError` type to represent errors returned from the snap-in\\xe2\\x80\\x99s run function. Developers can use this type to provide additional error details and indicate whether an error is retryable.\\n\\n[code]\\n\\n 1| class FunctionExecutionError extends Error { \\n ---|--- \\n 2| /** \\n 3| * Toggle to determine if", + "title": "Event reliability in DevRev snap-ins \u2014 DevRev | Docs" } ] }, @@ -3196,39 +3196,29 @@ "query": "associate multiple workspaces to a contact", "retrievals": [ { - "id": "ART-1210_KNOWLEDGE_NODE-0", - "text": "b'Workspaces | DevRev | Docs\\n\\n[![]()![]()](https://developer.devrev.ai/)\\n\\nPublic\\n\\nPublic\\n\\nSearch\\n\\n`/`\\n\\n[API Reference](/api-reference/getting-started)[rev-orgs](/api-reference/rev-orgs/workspaces)\\n\\nWorkspaces\\n==========\\n\\nCopy page\\n\\n`rev-orgs` endpoint\\n\\n\\xe2\\x84\\xb9\\xef\\xb8\\x8f Workspaces (or rev orgs) are the organizations that your customers belong to. A workspace offers more granularity than accounts to define the instances of your product. Users can be mapped to track", - "title": "Workspaces | DevRev | Docs" + "id": "ART-2000_KNOWLEDGE_NODE-25", + "text": "address.\\n\\nAccounts are associated with a workspace. An account can be a part of multiple workspaces at the same time. An account can also be linked to multiple opportunities. Accounts help you keep track of your customer contacts. Contacts are always linked to a workspace or an account.\\n\\nCreate an account\\n-----------------\\n\\nYou can create accounts in the following ways:\\n\\n### Using the DevRev app\\n\\n1. Go to **Accounts** > **+ Account**.\\n2. Fill in the details like account name,", + "title": "Accounts | Computer for Growth Teams | DevRev" }, { - "id": "ART-1414_KNOWLEDGE_NODE-1", - "text": "__\\n\\n[Pricing](https://devrev.ai/pricing)\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](https://devrev.ai/request-a-demo)\\n\\n[API Reference](/public/api-reference/getting-started)[rev-orgs](/public/api-reference/rev-orgs/workspaces)\\n\\n#\\n\\nWorkspaces\\n\\n`rev-orgs` endpoint\\n\\n\\xe2\\x84\\xb9\\xef\\xb8\\x8f Workspaces (or rev orgs) are the organizations that your customers belong to. A workspace offers more granularity than accounts to define the instances of your product. Users can be mapped", - "title": "Workspaces \u2014 DevRev | Docs" + "id": "ART-1986_KNOWLEDGE_NODE-30", + "text": "its own SLA, and a single customer can have multiple workspaces.\\n\\n**Adding assignment rules**\\n\\nGo to **Assignment rules** to add conditions for an account to be assigned a particular SLA.\\n\\n1. Click **+ Create Rule**.\\n2. In the **New SLA assignment rule** pane, select the account attributes and their values to check for.\\n3. Click **Save and Apply**.\\n\\n**Editing/Deleting an assignment rule**\\n\\nOnce an assignment rule is created, you have the option to edit or delete it. Any changes made", + "title": "Service-level agreement | Computer for Support Teams | DevRev" }, { "id": "ART-1960_KNOWLEDGE_NODE-28", - "text": "Individual prospects or users associated with an organization\\'s workspaces or accounts.\\n: Contacts can be associated with an account or workspace, but not always.\\n: Terms related to\\xc2\\xa0*contact*:\\n\\n * *[account](#account)*\\n * *[workspace](#workspace)*\\n: Read more about\\xc2\\xa0[*contact*](https://docs.devrev.ai/product/grow)\\n\\nconversation\\n\\n: An interaction between the builder and consumer that may be escalated to a ticket.\\n: Terms related", + "text": "Individual prospects or users associated with an organization\\'s workspaces or accounts.\\n: Contacts can be associated with an account or workspace, but not always.\\n: Terms related to\\xc2\\xa0*contact*:\\n\\n * *[account](#account)*\\n * *[workspace](#workspace)*\\n: Read more about\\xc2\\xa0[*contact*](https://docs.devrev.ai/product/grow)\\n\\nconversation\\n\\n: An interaction between the builder and consumer that may be escalated to a ticket.\\n: Terms related", "title": "Glossary | Computer by DevRev | DevRev" }, - { - "id": "ART-1210_KNOWLEDGE_NODE-1", - "text": "usage per workspace.\\n\\n\\xf0\\x9f\\x93\\x8c For more information about workspaces, refer to [Customers](https://docs.devrev.ai/product/customers).\\n\\nWas this page helpful?\\n\\nYesNo\\n\\n[Previous](/api-reference/parts/update)[#### Create Rev Org\\n\\nNext](/api-reference/rev-orgs/create)[Built with](https://buildwithfern.com/?utm_campaign=buildWith&utm_medium=docs&utm_source=developer.devrev.ai)'", - "title": "Workspaces | DevRev | Docs" - }, { "id": "ART-16264_KNOWLEDGE_NODE-29", - "text": "account.\\n + If both **Reported By** and **Account** fields are initially empty, you can search for and add any contact to the **Reported By** field, which will auto-fill the **Account** and **Workspace** (if applicable).\\n* **Handling multiple users:**\\n\\n + If all selected users within the **Reported By** field belong to the same workspace, the **Workspace** field remains unchanged.\\n + If users are from different workspaces, the **Workspace** field is emptied, while the **Account** field", + "text": "account.\\n + If both **Reported By** and **Account** fields are initially empty, you can search for and add any contact to the **Reported By** field, which will auto-fill the **Account** and **Workspace** (if applicable).\\n* **Handling multiple users:**\\n\\n + If all selected users within the **Reported By** field belong to the same workspace, the **Workspace** field remains unchanged.\\n + If users are from different workspaces, the **Workspace** field is emptied, while the **Account** field", "title": "June 2025 | Changelog | DevRev" }, { - "id": "ART-15506_KNOWLEDGE_NODE-17", - "text": "Contacts linked to the account | User and account information | Recommended for most B2B cases |\\n| **Three-level** | Account with linked workspaces and contacts | User, workspace and account information | Used for B2B cases but only recommended if your business model requires workspace organization |\\n\\n**What happens when you send different combinations:**\\n\\nUser reference:\\n\\n* A user reference is mandatory, ensuring its constant presence.\\n* If a user with the provided reference", - "title": "Identify your users with Plug | DevRev | Docs" - }, - { - "id": "ART-1414_KNOWLEDGE_NODE-2", - "text": "to track usage per workspace.\\n\\n\\xf0\\x9f\\x93\\x8c For more information about workspaces, refer to [Customers](https://docs.devrev.ai/product/customers).\\n\\nWas this page helpful?YesNo\\n\\n[ConceptsUp Next](/public/api-reference/tags/concepts)\\n\\n[Built with](https://buildwithfern.com/?utm_campaign=buildWith&utm_medium=docs&utm_source=developer.devrev.ai)\\n\\n[Enterprise grade security to protect customer dataLearn more about it.](https://devrev.ai/blog/soc-compliance)\\n\\nProduct\\n\\n *", - "title": "Workspaces \u2014 DevRev | Docs" + "id": "ART-1997_KNOWLEDGE_NODE-31", + "text": "users associated with an organization's workspaces or accounts. A contact is also known as a rev-user in the DevRev API.\\n\\nContacts represent customers, leads, and stakeholders with whom a business interacts. Contacts can be associated with an account or workspace, but not always.\\n\\n\\xf0\\x9f\\xa4\\x9d Engagement\\n------------\\n\\nDevRev uses engagements to capture all interactions between employees and customers, encompassing communications across various channels and touchpoints. DevRev records", + "title": "Computer for Growth Teams | DevRev" }, { "id": "ART-16784_KNOWLEDGE_NODE-6", @@ -3236,14 +3226,24 @@ "title": "Glossary" }, { - "id": "ART-1414_KNOWLEDGE_NODE-0", - "text": "b'[](/public/api-reference/rev-orgs/workspaces)\\n\\nPublic\\n\\n[](https://devrev.ai)\\n\\n * Product\\n * Platform\\n * Solutions\\n * Marketplace\\n * Company\\n * Resources\\n * [Pricing](https://devrev.ai/pricing)\\n\\n __\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](https://devrev.ai/request-a-demo)\\n\\n[](https://devrev.ai)\\n\\n __\\n\\nProduct __\\n\\nPlatform __\\n\\nSolutions __\\n\\nMarketplace __\\n\\nCompany __\\n\\nResources", - "title": "Workspaces \u2014 DevRev | Docs" + "id": "ART-2933_KNOWLEDGE_NODE-3", + "text": "associated with a workspace.\\n\\n##### \\n\\nJust want to get a token and get started? This [tutorial](/about/authentication#generate-a-personal-access-token-pat) teaches you the fastest way to get a token.\\n\\nYes\\n\\nNo\\n\\naccounts.create\\n\\nAccount is existing \\n\\'account ID\\'\\n\\nrev-orgs.list with \\n\\'account\\' filter\\n\\nrev-orgs.get with \\n\\'account ID\\'\\n\\nGet rev-org \\'display\\\\_id\\'\\n\\nCreate a \\'rev-user\\' under \\'contact\\'\\n\\nCreate an account\\n-----------------\\n\\nThe payload to make a", + "title": "Account creation | DevRev | Docs" }, { - "id": "ART-1997_KNOWLEDGE_NODE-31", - "text": "users associated with an organization's workspaces or accounts. A contact is also known as a rev-user in the DevRev API.\\n\\nContacts represent customers, leads, and stakeholders with whom a business interacts. Contacts can be associated with an account or workspace, but not always.\\n\\n\\xf0\\x9f\\xa4\\x9d Engagement\\n------------\\n\\nDevRev uses engagements to capture all interactions between employees and customers, encompassing communications across various channels and touchpoints. DevRev records", + "id": "ART-15506_KNOWLEDGE_NODE-17", + "text": "Contacts linked to the account | User and account information | Recommended for most B2B cases |\\n| **Three-level** | Account with linked workspaces and contacts | User, workspace and account information | Used for B2B cases but only recommended if your business model requires workspace organization |\\n\\n**What happens when you send different combinations:**\\n\\nUser reference:\\n\\n* A user reference is mandatory, ensuring its constant presence.\\n* If a user with the provided reference", + "title": "Identify your users with Plug | DevRev | Docs" + }, + { + "id": "ART-1997_KNOWLEDGE_NODE-28", + "text": "single account. This allows us to consolidate various workspaces under one account.\\n\\nTo create a new organization in DevRev:\\n\\n1. Click on your profile picture in the top left corner.\\n2. Go to the **Orgs** section and click on **+**.\\n3. Fill in the details and click **Create**.\\n4. Now you can find your newly created org in **Orgs**.\\n\\nIn modern SaaS applications, customers often create multiple workspaces for testing, production, and staging. All entities that drive support", "title": "Computer for Growth Teams | DevRev" + }, + { + "id": "ART-2035_KNOWLEDGE_NODE-31", + "text": "creating conversations from any Slack channel:\\n\\n1. Link the DevRev Customer workspace to the channel by running /devrev link in the channel.\\n2. In the pop-up modal, search for the DevRev Customer workspace. \\n 2a. Select the preferred workspace and click **Link**. \\n 2b. If your channel is already linked to a workspace, the modal will show the details of the workspace and an option to unlink.\\n3. Once linked, new contacts identified via Slack are automatically added to the associated", + "title": "Slack | Integrate | Snap-ins | DevRev" } ] }, @@ -3252,43 +3252,38 @@ "query": "Slack notifications org name unknown organisation", "retrievals": [ { - "id": "ART-2035_KNOWLEDGE_NODE-60", - "text": "hidden.\\n\\n![]()\\n\\nSlack currently does not support custom objects or related automations.\\n\\nSlack snap-in user resolution\\n-----------------------------\\n\\n* The Slack snap-in uses email for user resolution between platforms. If a user or organization hides their emails, the integration cannot resolve the user to a DevRev Contact and will act on behalf of itself instead. It's recommended to ask customers to share their emails with your organization so apps, including DevRev, can access", - "title": "Slack | Integrate | Snap-ins | DevRev" + "id": "ART-1283_KNOWLEDGE_NODE-2", + "text": "keyrings : 2 organization : 3 - name : my-secret-org-token 4 description : Enables access to organization-wide resources (e.g., Slack workspace) 5 types : 6 - devrev-keyring-type 7 display_name : Organization secret token 8 9 user : 10 - name : my-secret-user-token 11 description : Allows access to individual user resources (e.g., personal Google Calendar) 12 types : 13 - devrev-keyring-type 14 display_name : Your secret token\\n\\nBreakdown:\\n\\nname. : A unique identifier for the keyring in the", + "title": "Keyrings \u2014 DevRev | Docs" }, { - "id": "ART-2035_KNOWLEDGE_NODE-35", - "text": "the channel will not sync to DevRev.\\n\\nConversation notifications\\n--------------------------\\n\\nAny new message added to a conversation within your DevRev workspace, regardless of its originating source channel or platform, can trigger a notification in a designated Slack channel, helping your team stay updated on customer interactions.\\n\\n### To enable conversation notifications\\n\\n1. Turn on **Enable the conversation notification feature** in the Slack snap-in configuration.\\n2. Provide a", - "title": "Slack | Integrate | Snap-ins | DevRev" - }, - { - "id": "ART-2017_KNOWLEDGE_NODE-27", - "text": "Connection**.\\n * Select **Slack** from the dowpdown list.\\n * Give it a name and sign in with Slack. Ensure to toggle on **Make public** to make the connection public for your organization.\\n\\nConfigure the snap-in\\n---------------------\\n\\n1. In the **Configuration** tab, the first input field to set is *filters*. Here you can declare for which tickets to track the SLA status and to which channels to send notifications.\\n\\n Set the ticket subtype, severity, and part; the support heads", - "title": "SLA status change Slack notifier | Automate | Snap-ins | DevRev" + "id": "ART-1491_KNOWLEDGE_NODE-2", + "text": "keyrings : 2 organization : 3 - name : my-secret-org-token 4 description : Enables access to organization-wide resources (e.g., Slack workspace) 5 types : 6 - devrev-keyring-type 7 display_name : Organization secret token 8 9 user : 10 - name : my-secret-user-token 11 description : Allows access to individual user resources (e.g., personal Google Calendar) 12 types : 13 - devrev-keyring-type 14 display_name : Your secret token\\n\\nBreakdown:\\n\\nname. : A unique identifier for the keyring in the", + "title": "Keyrings \u2014 DevRev | Docs" }, { - "id": "ART-2035_KNOWLEDGE_NODE-36", - "text": "Slack Channel ID in the **Channel ID to send conversation notifications** snap-in configuration as the target to post notifications.\\n\\n* Any new message within tickets in the customer messages panel is also subjected to the same automation.\\n* To prevent notification overload, each conversation or ticket is subject to a five minute cooldown period between notifications. Multiple consecutive messages within this window will not trigger additional notifications.\\n* Notification threads are not", - "title": "Slack | Integrate | Snap-ins | DevRev" + "id": "ART-1276_KNOWLEDGE_NODE-18", + "text": "--- |\\n| 1 | const verifyOrgName = async (orgName: string, octokit: Octokit) => { |\\n| 2 | try { |\\n| 3 | await octokit.request(\"GET /orgs/{org}\", { |\\n| 4 | headers: { |\\n| 5 | \"X-GitHub-Api-Version\": \"2022-11-28\", |\\n| 6 | }, |\\n| 7 | org: orgName, |\\n| 8 | }); |\\n| 9 | } catch (error) { |\\n| 10 | console.error(error); |\\n| 11 | throw new Error(\"Invalid Organisation Name\"); |\\n| 12 | } |\\n| 13 | }; |\\n```\\n\\nSimilarly, the [GET", + "title": "Using a snap-in to perform an external action | DevRev | Docs" }, { - "id": "ART-2017_KNOWLEDGE_NODE-17", - "text": "* [Email snap-in configuration](/docs/integrations/email-config)\\n - [Exotel](/docs/integrations/exotel)\\n - [Slack](/docs/integrations/slack)\\n - [WhatsApp](/docs/integrations/whatsapp)\\n - [GitHub](/docs/integrations/github)\\n - [GitLab](/docs/integrations/gitlab)\\n - [Harness](/docs/integrations/harness)\\n - [Marker.io](/docs/integrations/marker-io)\\n - [Instabug](/docs/integrations/instabug)\\n - [Qase](/docs/integrations/qase)\\n - [Tracxn", - "title": "SLA status change Slack notifier | Automate | Snap-ins | DevRev" + "id": "ART-1276_KNOWLEDGE_NODE-17", + "text": "getOrgAndRepoNames = (paramString: string): string[] => { |\\n| 2 | const paramList = paramString.split(\" \"); |\\n| 3 | if (paramList.length !== 2) { |\\n| 4 | throw new Error(\"Invalid Parameters\"); |\\n| 5 | } |\\n| 6 | const [orgName, repoName] = paramList; |\\n| 7 | return [orgName, repoName]; |\\n| 8 | }; |\\n```\\n\\nThe GitHub REST API () is used to confirm the specified organisation name.\\n\\n```\\n| | |\\n| --- |", + "title": "Using a snap-in to perform an external action | DevRev | Docs" }, { - "id": "ART-4199_KNOWLEDGE_NODE-31", - "text": "Policy](/legal/cookie-policy)\\n* [Privacy Policy](/legal/privacy-policy)\\n* [Terms of Service](/legal/terms-of-service)\\n\\n[System Status](/status)\\n\\n\\xc2\\xa9 2025 DevRev Inc.\"", - "title": "Slack message agent | Automate | Snap-ins | DevRev" + "id": "ART-2035_KNOWLEDGE_NODE-42", + "text": "ticket notifications\\n\\n* Enable through the **Notify on new ticket creation** snap-in configuration.\\n* Provide a Slack channel ID in the **Channel ID to send ticket notifications** configuration.\\n* Snap-in will send notifications to the target channel whenever a new ticket is created, regardless of the source channel or platform.\\n* Notification message threads are **not** synced between platforms.\\n\\n### Notifications for ticket state update\\n\\n* Enable through **Notify on ticket state", + "title": "Slack | Integrate | Snap-ins | DevRev" }, { - "id": "ART-2017_KNOWLEDGE_NODE-16", - "text": "sync](/docs/automations/ticket-linked-issues-comment-sync)\\n - [Slack message agent](/docs/automations/slack-message-agent)\\n + [Integrate](/docs/integrate)\\n\\n - [Bitbucket](/docs/integrations/bitbucket)\\n - [Calendly](/docs/integrations/calendly)\\n - [Coralogix security integration](/docs/integrations/coralogix)\\n - [Datadog](/docs/integrations/datadog)\\n - [Google Calendar AirSync](/docs/integrations/google-calendar-airdrop)\\n - [Email](/docs/integrations/email)\\n\\n", - "title": "SLA status change Slack notifier | Automate | Snap-ins | DevRev" + "id": "ART-12395_KNOWLEDGE_NODE-26", + "text": "docs](/docs/integrations/slack?_gl=1*sit0d5*_ga*MTkzMTU5ODIyOS4xNzE5ODEyMjEw*_ga_MK3C9L001S*czE3NDc2NjIxOTkkbzEzNTkkZzEkdDE3NDc2NjIyMzMkajAkbDAkaDA).\\n\\nFeatures\\n--------\\n\\n* **Customer release notes**: Automatically share release notes with customers via Slack Connect channels.\\n* **Account linking**: Link Slack channels to accounts using the /slack\\\\_broadcaster\\\\_link command in the account timeline. To unlink, use /slack\\\\_broadcaster\\\\_link invalid.\\n* **Bulk account", + "title": "Slack Broadcaster | Automate | Snap-ins | DevRev" }, { - "id": "ART-2017_KNOWLEDGE_NODE-24", - "text": "[Product demos](/docs/DevRevU/demos)\\n\\nOn this page\\n\\n* [Installation](#installation)\\n* [Configure the snap-in](#configure-the-snapin)\\n\\n1. [Documentation](/docs)\\n3. [Snap-ins](/docs/snapins)\\n[Automate](/docs/automate)\\n[SLA status change Slack notifier](/docs/automations/sla-change-notifier)\\n\\nSLA status change Slack notifier\\n================================\\n\\nGet alerted on your ticket\\'s SLAs. This snap-in sends a notification through Slack to user configured channels, tagging the", + "id": "ART-2017_KNOWLEDGE_NODE-28", + "text": "you would like to tag on the message (the ticket owner gets tagged automatically); and the target Slack channel. The channel\\'s ID can be found by going to the channel details. Refer to the placeholder value on the input to see an example of how this looks.\\n2. Decide if notifications should go out even if the ticket has a target end date set. Set the toggle to the desired behavior.\\n3. Decide if a ticket should pass the check if it\\'s part is a descendant of the filter part. For example, if a", "title": "SLA status change Slack notifier | Automate | Snap-ins | DevRev" }, { @@ -3297,9 +3292,14 @@ "title": "Slack | Integrate | Snap-ins | DevRev" }, { - "id": "ART-4199_KNOWLEDGE_NODE-23", - "text": "2025](/docs/changelog/_2025-06-01)\\n + [May 2025](/docs/changelog/_2025-05-01)\\n + [March and April 2025](/docs/changelog/_2025-04-01)\\n + [February 2025](/docs/changelog/_2025-02-01)\\n* [Developer \\xe2\\x86\\x97\\xef\\xb8\\x8f](https://developer.devrev.ai/)\\n* [DevRevU \\xe2\\x86\\x97\\xef\\xb8\\x8f](/docs/DevRevU)\\n\\n + [Product demos](/docs/DevRevU/demos)\\n\\nOn this page\\n\\n* [Install](#install)\\n* [Configure the custom Slack bot](#configure-the-custom-slack-bot)\\n* [Configure", - "title": "Slack message agent | Automate | Snap-ins | DevRev" + "id": "ART-1484_KNOWLEDGE_NODE-98", + "text": "\\n 3| \"action_id\": \"emails\", \\n 4| \"placeholder\": { \\n 5| \"text\": \"Enter email here\", \\n 6| \"type\": \"plain_text\" \\n 7| }, \\n 8| \"type\": \"email_list\" \\n 9| }, \\n 10| \"hint\": { \\n 11| \"text\": \"When these emails are included in a Slack message, they automatically receive an email notification.\", \\n 12| \"type\": \"plain_text\" \\n 13| }, \\n 14| \"label\": { \\n 15| \"text\": \"List of emails\", \\n 16|", + "title": "Snapkit \u2014 DevRev | Docs" + }, + { + "id": "ART-1278_KNOWLEDGE_NODE-10", + "text": "as the\\nconduit for receiving relevant events.\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | event_sources: |\\n| 2 | organization: |\\n| 3 | - name: github-app-source |\\n| 4 | type: flow-custom-webhook |\\n| 5 | description: Event coming from Github app. |\\n| 6 | config: |\\n| 7 | policy: | |\\n| 8 | package rego |\\n| 9 | signature := crypto.hmac.sha256(base64.decode(input.request.body_raw), input.parameters.secret) |\\n| 10 | expected_header := sprintf(\"sha256=%v\", [signature]) |\\n| 11 |", + "title": "Snap-in triggered by an external source | DevRev | Docs" } ] }, @@ -3307,55 +3307,55 @@ "query_id": "5008d8ba-33fe-4763-b515-5934672610d1", "query": "how to create tickets in DevRev MVP org", "retrievals": [ - { - "id": "ART-1979_KNOWLEDGE_NODE-27", - "text": "also be used to engage customers for feedback/ideas (such as new feature ideas). Scoping is important for broadcast tickets as there needs to be a differentiation between broadcast (all revs) vs. multicast (particular revs).\\n\\nViews of tickets can be found under **Support** in the DevRev app.\\n\\n![]()\\n\\nYou can export views to CSV or JSON by selecting **Actions** in the upper-right corner and choosing the format.\\n\\nAttributes\\n----------\\n\\nTickets have attributes that can be used to filter", - "title": "Tickets | Computer for Support Teams | DevRev" - }, { "id": "ART-1979_KNOWLEDGE_NODE-37", "text": "filters and **Group** conditions across various vistas in DevRev to track specific work, capacity, and more.\\n\\nYou can add custom attributes to tickets to track additional information. For more information on custom attributes, see [object customization](./object-customization).\\n\\nIssues are attached to tickets in order to track efforts with product priorities.\\n\\nCreate a ticket\\n---------------\\n\\n1. Go to **Support** > **Tickets** from the sidebar on the left.\\n2. Click **New Ticket** on", "title": "Tickets | Computer for Support Teams | DevRev" }, { - "id": "ART-1447_KNOWLEDGE_NODE-1", - "text": "[Tickets](https://docs.devrev.ai/product/tickets) and [Issues](https://docs.devrev.ai/product/issues).\\n\\nWas this page helpful?YesNo\\n\\n[Create WorkUp Next](/public/api-reference/works/create)\\n\\n[Built with](https://buildwithfern.com/?utm_campaign=buildWith&utm_medium=docs&utm_source=developer.devrev.ai)\\n\\n[Enterprise grade security to protect customer dataLearn more about it.](https://devrev.ai/blog/soc-compliance)\\n\\nProduct\\n\\n * [Build](https://devrev.ai/build)\\n *", - "title": "Tickets and issues \u2014 DevRev | Docs" + "id": "ART-12390_KNOWLEDGE_NODE-29", + "text": "Ticket | Creates a new ticket in DevRev. | * Ticket details like title, body, applies\\\\_to\\\\_part, etc. * subtype: (Optional) Ticket subtype * apps: (Optional) Related apps * app\\\\_custom\\\\_fields: (Optional) Custom fields | Created ticket object |\\n| Convert Conversation To Ticket | Converts a conversation to a ticket. | * conversation\\\\_id: ID of the conversation to convert | ticket\\\\_id: ID of the created ticket |\\n\\nObject retrieval\\n----------------\\n\\n| Operation | Description | Input", + "title": "Workflow action library | Workflows | Computer by DevRev | DevRev" }, { - "id": "ART-1605_KNOWLEDGE_NODE-461", - "text": "need response.\\nticket.rev_org string Optional\\nFilters for tickets that are associated with any of the provided Rev organizations.\\nticket.severity enum Optional\\nFilters for tickets with any of the provided severities.\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\nFilters for records with any of the provided SLA stages.\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\nFilters for tickets with any of the", - "title": "Create \u2014 DevRev | Docs" + "id": "ART-1483_KNOWLEDGE_NODE-18", + "text": "the code\\n\\nUpdate the code in `src/functions/ticket_creator/index.ts` to reflect the behavior.\\n\\nFirstly, import the DevRev TypeScript SDK in the `index.ts` file\\n\\nindex.ts\\n\\n[code]\\n\\n 1| import {client, publicSDK} from \"@devrev/typescript-sdk\"; \\n ---|---\\n[/code] \\n \\nNext, update the `run` function in the hello-world example. Since the ticket gets created frequently, set some creation time in the title and the body. The example uses the part as `PROD-1` and keeps the owner as", + "title": "Using a snap-in to perform a DevRev action \u2014 DevRev | Docs" }, { - "id": "ART-1785_KNOWLEDGE_NODE-459", - "text": "need response.\\nticket.rev_org string Optional\\nFilters for tickets that are associated with any of the provided Rev organizations.\\nticket.severity enum Optional\\nFilters for tickets with any of the provided severities.\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\nFilters for records with any of the provided SLA stages.\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\nFilters for tickets with any of the", - "title": "Create \u2014 DevRev | Docs" + "id": "ART-2039_KNOWLEDGE_NODE-25", + "text": "create DevRev tickets from Marker.io issues, you can configure the\\nsnap-in to use this email to auto-fill the **Reported By** and **Customer\\nWorkspace** fields in tickets. If no contact or accounts match the email, they\\nare automatically created.\\n\\nInstalling the Marker.io integration snap-in\\n--------------------------------------------\\n\\n1. Install the [Marker.io](/marketplace/marker-io) from the\\n DevRev Marketplace.\\n2. Configure the snap-in as needed.\\n\\n * (Optional) Select the", + "title": "Marker.io | Integrate | Snap-ins | DevRev" }, { - "id": "ART-1832_KNOWLEDGE_NODE-468", - "text": "need response.\\nticket.rev_org string Optional\\nFilters for tickets that are associated with any of the provided Rev organizations.\\nticket.severity enum Optional\\nFilters for tickets with any of the provided severities.\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\nFilters for records with any of the provided SLA stages.\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\nFilters for tickets with any of the", - "title": "Create \u2014 DevRev | Docs" + "id": "ART-2047_KNOWLEDGE_NODE-38", + "text": "type, it must be marked for syncing. Marking a DevRev ticket for syncing can only be done during the creation of a new ticket. During ticket creation, open the dropdown **Select Subtype**, set it to the type the ticket should be synced to. The format is as follows: SalesforceService / {type}.\\n\\nFor example, if you want to sync a new ticket in DevRev to a case type in Salesforce, this would show as **SalesforceService / cases**.\\n\\nAfter a DevRev work item has been marked for syncing, it\\'s", + "title": "Salesforce AirSync | AirSync | Snap-ins | DevRev" }, { - "id": "ART-4177_KNOWLEDGE_NODE-5", - "text": "Users, Not tickets\\n--------------------------\\n\\nDelve into the ways by which you can delight customers and build strong brand association early on, using DevRev.\\n\\n[![]()\\n\\nIntroducing Conversations and Inbox\\n\\nDelve into the basics of the DevRev Inbox and understand how to manage different types of customer conversations](https://vimeo.com/1027655861)[![]()\\n\\nExploring tickets and their attributes\\n\\nLearn more about the different stages on tickets, and how progress is communicated", - "title": "DevRev University - DevRev for Startups" + "id": "ART-1361_KNOWLEDGE_NODE-0", + "text": "b'Create Work | DevRev | Docs\\n\\n[![]()![]()](https://developer.devrev.ai/)\\n\\nPublic\\n\\nPublic\\n\\nSearch\\n\\n`/`\\n\\n[API Reference](/api-reference/getting-started)[works](/api-reference/works/tickets-and-issues)\\n\\nCreate Work\\n===========\\n\\nCopy page\\n\\nPOST\\n\\nhttps://api.devrev.ai/works.create\\n\\nPOST\\n\\n/works.create\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl -X POST https://api.devrev.ai/works.create \\\\ |\\n| > | -H \"Authorization: Bearer \" \\\\ |\\n| > | -H \"Content-Type:", + "title": "Create Work | DevRev | Docs" }, { - "id": "ART-1979_KNOWLEDGE_NODE-23", - "text": "2025](/docs/changelog/_2025-06-01)\\n + [May 2025](/docs/changelog/_2025-05-01)\\n + [March and April 2025](/docs/changelog/_2025-04-01)\\n + [February 2025](/docs/changelog/_2025-02-01)\\n* [Developer \\xe2\\x86\\x97\\xef\\xb8\\x8f](https://developer.devrev.ai/)\\n* [DevRevU \\xe2\\x86\\x97\\xef\\xb8\\x8f](/docs/DevRevU)\\n\\n + [Product demos](/docs/DevRevU/demos)\\n\\nOn this page\\n\\n* [Attributes](#attributes)\\n* [Create a ticket](#create-a-ticket)\\n* [Tags](#tags)\\n* [Stages](#stages)\\n*", - "title": "Tickets | Computer for Support Teams | DevRev" + "id": "ART-3235_KNOWLEDGE_NODE-25", + "text": "one.\\n\\nInstallation\\n------------\\n\\nInstall the [Reported by Enricher](https://marketplace.devrev.ai/ticket-reported-by) from DevRev marketplace.\\n\\nConfiguration\\n-------------\\n\\nIn the **Configuration** tab, the following settings are available:\\n\\n* **Custom Email Field**: Specify the backend name of the custom field where the email is entered when creating a ticket.\\n* **Default Account**: Select the account to which new customers should be linked if they do not already exist in the", + "title": "Reported by enricher | Automate | Snap-ins | DevRev" + }, + { + "id": "ART-1978_KNOWLEDGE_NODE-33", + "text": "tickets but also all the tickets raised by the other users from their organization. You can add multiple customer admins from the same customer organization.\\n\\nOnly verified users can login into the portal.\\n\\nTo create a verified user:\\n\\n1. Go to **Accounts** in the DevRev app and create an account.\\n2. Create a contact under **Contacts** and link it to the account.\\n\\n### Set up customer admins\\n\\nTo set up customer admins, follow these steps:\\n\\n1. Log in on your DevRev app with your", + "title": "Customer portal | Computer for Support Teams | DevRev" }, { - "id": "ART-1447_KNOWLEDGE_NODE-7", - "text": "Inc.\\n\\n[](https://devrev.ai)\\n\\n * Product\\n * Platform\\n * Solutions\\n * Marketplace\\n * Company\\n * Resources\\n * [Pricing](https://devrev.ai/pricing)\\n\\n __\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](https://devrev.ai/request-a-demo)\\n\\n[](https://devrev.ai)\\n\\n __\\n\\nProduct __\\n\\nPlatform __\\n\\nSolutions __\\n\\nMarketplace __\\n\\nCompany __\\n\\nResources __\\n\\n[Pricing](https://devrev.ai/pricing)\\n\\n[Login](https://app.devrev.ai/login)[Book a", - "title": "Tickets and issues \u2014 DevRev | Docs" + "id": "ART-1275_KNOWLEDGE_NODE-18", + "text": "= `Ticket created at ${date.toLocaleString()}`; |\\n| 14 | const ticketBody = `This ticket was created by a snap-in at ${date.toLocaleString()}`; |\\n| 15 | |\\n| 16 | const response = await devrevSDK.worksCreate({ |\\n| 17 | title: ticketName, |\\n| 18 | body: ticketBody, |\\n| 19 | // The ticket is created in the PROD-1 part. Rename this to match your part. |\\n| 20 | applies_to_part: \"PROD-1\", |\\n| 21 | // The ticket is owned by the DEVU-1 user. Rename this to match the required user. |\\n| 22 |", + "title": "Using a snap-in to perform a DevRev action | DevRev | Docs" }, { - "id": "ART-1447_KNOWLEDGE_NODE-8", - "text": "demo](https://devrev.ai/request-a-demo)\\n\\n'", - "title": "Tickets and issues \u2014 DevRev | Docs" + "id": "ART-4185_KNOWLEDGE_NODE-25", + "text": "marketplace.\\n\\nInstallation\\n------------\\n\\n1. In DevRev, go to **Settings** > **Snap-ins** and click **Explore Marketplace** in the top-right corner.\\n2. In the DevRev marketplace, find **Ticket approval workflow** and click **Install**.\\n3. In DevRev, **Snap-ins** > **Ticket approval workflow** > **Configure**.\\n4. Enter the required parameters like **Delay in seconds**.\\n5. Click **Save** and **Install snap-in**.\\n\\nUsage\\n-----\\n\\nOn the ticket execute the /request\\\\_approval command with", + "title": "Ticket approval workflow | Automate | Snap-ins | DevRev" } ] }, @@ -3364,54 +3364,54 @@ "query": "manage multiple email addresses for one account", "retrievals": [ { - "id": "ART-888_KNOWLEDGE_NODE-48", - "text": "you use an email address provided by an organization (such as your work email address) to access the Services, then the owner of the domain associated with your email address (e.g. your employer) may assert administrative control over your account and use of the Services at a later date. You will be notified if this happens.If you do not want an administrator to be able to assert control over your account or use of the Services, you should deactivate your membership with the relevant", - "title": "Privacy Policy" + "id": "ART-3207_KNOWLEDGE_NODE-45", + "text": "snap-in. These only appear once the email snap-in is successfully installed and verified.\\n\\nSet-up the provided forwarding address to the account you want to forward from. For example support@example.com.\\n\\nIn the DevRev app, under the **Instructions** tab you can see a forwarding email address displayed as v\\\\_\\\\_\\\\_\\\\_\\\\_\\\\_\\\\_\\\\_\\\\_\\\\_\\\\_@hooks.devrev.ai. This is the address where you can forward your support emails.\\n\\nGoogle Workspace/Groups\\n\\n1. If you are using Google Groups, add your", + "title": "Email snap-in configuration | Email | Integrate | Snap-ins | DevRev" }, { - "id": "ART-888_KNOWLEDGE_NODE-49", - "text": "enterprise, or use your personal email address to register for or access the Services. If an administrator has not already asserted control over your account or access to the Services, you can update the email address associated with your account through your account settings in your profile. Once an administrator asserts control over your account or use of the Services, you will no longer be able to change the email address associated with your account without administrator approval.Please", - "title": "Privacy Policy" + "id": "ART-4020_KNOWLEDGE_NODE-25", + "text": "account.\\n2. Generate an **API key**.\\n3. Create a SendGrid connection:\\n a. Go to **Settings** > **Snap-ins** > **+ Connection**\\n b. Select **SendGrid**.\\n c. Add the **API key** and click **Save**.\\n\\nInstallation\\n------------\\n\\n1. Install the [**send customized emails**](https://marketplace.devrev.ai/marketplace/send-emails) from the DevRev marketplace.\\n2. Open the Workflow Builder and locate the **send customized emails** action node.\\n3. Configure the node by selecting the", + "title": "Send customized emails | Automate | Snap-ins | DevRev" }, { - "id": "ART-2027_KNOWLEDGE_NODE-45", - "text": "due to mail loops, the email integration has the provision to specify user-specific email limits. By default, the user-specific limit is set to 30 emails per 10 minutes.\\n\\nIf a user sends 30 emails in a 10-minute time frame, this particular user is marked with the tag spammer. Once marked as a spammer, the user can only send 100 emails in a 24-hour period. All of these emails are marked as spam by the system. Any emails beyond the 100 spam email default limit are dropped, and the blocked tag", - "title": "Email | Integrate | Snap-ins | DevRev" + "id": "ART-2575_KNOWLEDGE_NODE-28", + "text": "a database identifier or an email address.)\\n* account\\\\_external\\\\_reference (the external reference of the contact\\'s parent account)\\n\\n### Array fields\\n\\nFor fields that accept multiple values, such as **owners** and **industry**, values should be separated by commas (,). For example, Agriculture and Forestry should be written as Agriculture,Forestry.\\n\\n![]()\\n\\nIf a value contains a comma, enclose it in backticks. For example, enter \"Rail, Bus & Taxi\" as `Rail, Bus & Taxi`.\\n\\n###", + "title": "Account and contact import | Computer for Growth Teams | DevRev" }, { - "id": "ART-2027_KNOWLEDGE_NODE-27", - "text": "track interactions (**Support > Inbox** for conversations and **Support > Tickets** for tickets). All replies are sent from your organization\\xe2\\x80\\x99s own email addresses, maintaining a professional and personalized customer experience that strengthens your brand and fosters better engagement. This method builds trust with mailbox providers and recipients across any email service, reducing spam flags and protecting your brand identity by adhering to DMARC standards.\\n\\nYou can choose for an", - "title": "Email | Integrate | Snap-ins | DevRev" + "id": "ART-3207_KNOWLEDGE_NODE-57", + "text": "connection](#1-create-a-new-connection)\\n* [2. Configure email integration snap-in](#2-configure-email-integration-snapin)\\n* [Next steps for configuration of the snap-in](#next-steps-for-configuration-of-the-snapin)\\n* [Step 1: Add a Primary Email Address](#step-1-add-a-primary-email-address)\\n* [Step 2: Define the Primary Use Case](#step-2-define-the-primary-use-case)\\n* [Step 3: Add Additional Support Emails](#step-3-add-additional-support-emails)\\n* [Step 4: Set the Default Part and", + "title": "Email snap-in configuration | Email | Integrate | Snap-ins | DevRev" }, { - "id": "ART-2032_KNOWLEDGE_NODE-31", - "text": "creators. Enter multiple emails separated by commas.\\n * **Add non-existing customers**: Enable this to allow people in meetings who are not already customers to be added as customers.\\n\\nIf a meeting is scheduled with people who are neither part of the company nor existing customers, this option allows them to be added as customers.\\n\\n* **Track meetings from free email domains**: Enable this feature to capture meetings scheduled using non-work email addresses, such as gmail.com or", - "title": "Google Calendar | Integrate | Snap-ins | DevRev" + "id": "ART-888_KNOWLEDGE_NODE-49", + "text": "enterprise, or use your personal email address to register for or access the Services. If an administrator has not already asserted control over your account or access to the Services, you can update the email address associated with your account through your account settings in your profile. Once an administrator asserts control over your account or use of the Services, you will no longer be able to change the email address associated with your account without administrator approval.Please", + "title": "Privacy Policy" }, { - "id": "ART-2575_KNOWLEDGE_NODE-17", - "text": "* [Email snap-in configuration](/docs/integrations/email-config)\\n - [Exotel](/docs/integrations/exotel)\\n - [Slack](/docs/integrations/slack)\\n - [WhatsApp](/docs/integrations/whatsapp)\\n - [GitHub](/docs/integrations/github)\\n - [GitLab](/docs/integrations/gitlab)\\n - [Harness](/docs/integrations/harness)\\n - [Marker.io](/docs/integrations/marker-io)\\n - [Instabug](/docs/integrations/instabug)\\n - [Qase](/docs/integrations/qase)\\n - [Tracxn", - "title": "Account and contact import | Computer for Growth Teams | DevRev" + "id": "ART-3207_KNOWLEDGE_NODE-46", + "text": "support address as a member of the Google Group.\\n\\n You must be a part of the group and have permission to send emails to the Google Group.\\n2. Go to the settings of your support Gmail account.\\n3. Navigate to **Forwarding and POP/IMAP** and add the forwarding email address v\\\\_\\\\_\\\\_\\\\_\\\\_\\\\_\\\\_\\\\_\\\\_\\\\_\\\\_@hooks.devrev.ai. Click **Next**.\\n4. Click **Proceed** when you are redirected to a new webpage. You are asked for a confirmation code sent to this forwarding address.\\n5. If the", + "title": "Email snap-in configuration | Email | Integrate | Snap-ins | DevRev" }, { - "id": "ART-3207_KNOWLEDGE_NODE-38", - "text": "Step 2: Define the Primary Use Case\\n\\nChoose how DevRev should interpret emails sent to the primary address:\\n\\n* Choose between generating a **Ticket or a Conversation** from the incoming email.\\n\\nToggle on **Set email as the default channel for tickets** to ensure that:\\n\\n* Customer chat replies are sent via email as well as to the original source of the channel.\\n\\n### Step 3: Add Additional Support Emails\\n\\nYou can add more addresses to handle support requests.\\n\\n* **Tickets**: Emails", - "title": "Email snap-in configuration | Email | Integrate | Snap-ins | DevRev" + "id": "ART-2045_KNOWLEDGE_NODE-51", + "text": "email: [a@example.com](mailto:a@example.com) account: **None** | email: [a@example.com](mailto:a@example.com) account: **None** | Existing contact used |\\n| email: [a@example.com](mailto:a@example.com) account: \"Example\" | email: [a@example.com](mailto:a@example.com) account: \"Example\" | Existing contact used |\\n| email: [a@example.com](mailto:a@example.com) account: \"Example\" | email: [a@example.com](mailto:a@example.com) account: **None** | New contact created |\\n| email:", + "title": "AirSync | Snap-ins | DevRev" }, { - "id": "ART-1953_KNOWLEDGE_NODE-27", - "text": "conversation, ensuring seamless and continuous communication.\\n\\nBy default, notifications are sent from [notifications@devrev.ai](mailto:notifications@devrev.ai). However, this setting can be overridden to use the organization\\xe2\\x80\\x99s primary email address as the sender, or notifications can be turned off entirely.\\n\\nTo configure the notifications setting, under [**Settings** > **Snap-ins** > **Email Integration**](https://app.devrev.ai/devrev/settings/snap-ins/email-with-tickets), go to", - "title": "Customer email notifications | Computer by DevRev | DevRev" + "id": "ART-1401_KNOWLEDGE_NODE-2", + "text": "starts from the beginning.\\n\\nemaillist of stringsOptional\\n\\nFilters Dev users based on email addresses.\\n\\nexternal_identity.idstringOptional`format: \"text\"`\\n\\nUnique ID of the user in the external source.\\n\\nexternal_identity.issuerstringOptional`format: \"text\"`\\n\\nIssuer of the external identity of the user.\\n\\nlimitintegerOptional\\n\\nThe maximum number of Dev users to return. The default is \\xe2\\x80\\x9850\\xe2\\x80\\x99.\\n\\nmodeenumOptional\\n\\nThe iteration mode to use, otherwise if not set,", + "title": "List Dev Users \u2014 DevRev | Docs" }, { - "id": "ART-3207_KNOWLEDGE_NODE-26", - "text": "Configure email forwarding for your email provider](#3-configure-email-forwarding-for-your-email-provider)\\n* [4. Verify configuration](#4-verify-configuration)\\n* [5. Events Panel](#5-events-panel)\\n\\n1. [Documentation](/docs)\\n3. [Snap-ins](/docs/snapins)\\n[Integrate](/docs/integrate)\\n[Email](/docs/integrations/email)\\n[Email snap-in configuration](/docs/integrations/email-config)\\n\\nEmail snap-in configuration\\n===========================\\n\\n1. Create a new", - "title": "Email snap-in configuration | Email | Integrate | Snap-ins | DevRev" + "id": "ART-1978_KNOWLEDGE_NODE-34", + "text": "registered email address and go to **Settings** > **User management** > **Groups > Customer Admins**.\\n2. Select the **Add User** option in the top-right corner to search for the customer whom you want to designate as a customer admin.\\n\\n### Customer portal login methods\\n\\nThe customer portal supports three login methods:\\n\\n1. Email OTP (One-Time Password): User enters their email, receives a one-time code, and enters it to log in.\\n2. SSO: Users log in through organization\\xe2\\x80\\x99s", + "title": "Customer portal | Computer for Support Teams | DevRev" }, { - "id": "ART-2575_KNOWLEDGE_NODE-3", - "text": "management](/docs/product/workflow-management)\\n - [Workflow nodes](/docs/product/workflow-nodes)\\n - [Troubleshooting](/docs/product/troubleshooting-workflows)\\n + [Templates](/docs/product/template)\\n + [Accessing DevRev](/docs/product/ui)\\n + [External identity provider setup](/docs/product/sso-saml)\\n + [Remote MCP server](/docs/product/remote-mcp)\\n* [Computer for Support Teams](/docs/product/support)\\n\\n + [Inbox](/docs/product/inbox)\\n + [Support", - "title": "Account and contact import | Computer for Growth Teams | DevRev" + "id": "ART-3207_KNOWLEDGE_NODE-37", + "text": "href=\"mailto:support@devrev.ai\">support@devrev.ai\\n\\n\\n\\n18 \\n\\n\\n\\n19 \\n\\n\\n\\n20 \\n```\\n\\nShow more\\n```\\n\\n**Result**:\\n\\n![]()\\n\\n### Next steps for configuration of the snap-in\\n\\n### Step 1: Add a Primary Email Address\\n\\n* Format: Name \\xe2\\x80\\x94 this is what appears in the customer\\xe2\\x80\\x99s inbox.\\n* Example: Maple Support \\n\\nThis email address becomes the primary channel for incoming support mail.\\n\\n###", + "title": "Email snap-in configuration | Email | Integrate | Snap-ins | DevRev" } ] }, @@ -3420,24 +3420,19 @@ "query": "how to install PLuG website installation PLuG ID setup guide", "retrievals": [ { - "id": "ART-2059_KNOWLEDGE_NODE-7", - "text": "these steps.\\n\\nIn DevRev, go to Settings. > Support. > PLuG Settings. through the settings icon in the top-left corner.\\nClick Enable PLuG Widget. if it isn\\'t already enabled.\\nCopy your Unique App ID. from the Configuration tab..\\nSetup for HTML.\\n\\nPlace this code in the head of your HTML page.\\n\\n1 //\\n2 < script\\n3 type = \"text/javascript\"\\n4 src = \"https://plug-platform.devrev.ai/static/plug.js\"\\n5 > \\n\\nPlace this code in the body of your HTML page.\\n\\n1 < script >\\n2", - "title": "Install PLuG chat on your website" + "id": "ART-2893_KNOWLEDGE_NODE-0", + "text": "b'[](/public/sdks/web/installation)\\n\\nPublic\\n\\nOn this page\\n\\n * [Getting your unique app ID](/public/sdks/web/installation#getting-your-unique-app-id)\\n\\n[SDKs](/public/sdks)[PLuG Web SDK](/public/sdks/web/installation)\\n\\n#\\n\\nInstall the Web SDK\\n\\nTo install the PLuG SDK on your website or web application, insert the code snippet provided below on every page where you want the SDK to be active. Once the SDK is installed, the chat widget appears by default.\\n\\n## Getting your unique app", + "title": "Install the Web SDK \u2014 DevRev | Docs" }, { - "id": "ART-2059_KNOWLEDGE_NODE-10", - "text": "users that come to your site and haven\\'t yet logged in or shared any information.\\n\\nWe understand the importance of making your engagement more personalized and contextual with your customers. Learn how to identify your customers and update their information.\\n\\nPrevious PLuG Next Install PLuG search on your website\\nOn this page\\n\\nIntegration code Unique app ID Setup for HTML Setup for React\\n\\nEnterprise grade security to protect customer data\\nLearn more about it.\\nProduct\\n\\nBuild", - "title": "Install PLuG chat on your website" - }, - { - "id": "ART-2059_KNOWLEDGE_NODE-6", - "text": "to the Customize documentation.\\n\\nAlternatively, for the most comprehensive customizations, refer to our SDK functions here.\\n\\nIntegration code.\\n\\nTo get the PLuG chat widget to appear on your website and web app, copy and paste the snippet below on every page where you want the widget to appear for website visitors.\\n\\nUnique app ID.\\n\\nMake sure to replace the app ID with your app ID which identifies your PLuG chat widget. You can access your app ID from your DevRev account by following", + "id": "ART-2059_KNOWLEDGE_NODE-9", + "text": "App.js.\\n\\n1 useEffect ( () => {\\n2 window. plugSDK. init ({\\n3 // Please ensure you replace the app_id with your unique app id\\n4 app_id : \"\" ,\\n5 });\\n6 }, []);\\n\\nYou should now have PLuG chat widget installed on your website. Facing some issues? Reach out to us through our own PLuG chat widget from the bottom right of your screen.\\n\\nOnce the widget is installed on your website, every user who visits your website is considered an anonymous user. Anonymous users are the", "title": "Install PLuG chat on your website" }, { - "id": "ART-2059_KNOWLEDGE_NODE-12", - "text": "width=\"0\" style=\"display:none;visibility:hidden\">'", - "title": "Install PLuG chat on your website" + "id": "ART-2894_KNOWLEDGE_NODE-2", + "text": "insert the code snippet provided below on every page where you want the widget to appear for website visitors.\\n\\n## Unique app ID\\n\\nEnsure to replace the app ID with your app ID which identifies your PLuG search widget. You can access your app ID from your DevRev account by following these steps.\\n\\n 1. In DevRev, go to **Settings** > **Support** > **PLuG Settings** through the settings icon in the top-left corner.\\n 2. Click **Enable PLuG Widget** if it isn\\xe2\\x80\\x99t already enabled.\\n", + "title": "Install PLuG search \u2014 DevRev | Docs" }, { "id": "ART-2059_KNOWLEDGE_NODE-5", @@ -3445,29 +3440,34 @@ "title": "Install PLuG chat on your website" }, { - "id": "ART-2059_KNOWLEDGE_NODE-9", - "text": "App.js.\\n\\n1 useEffect ( () => {\\n2 window. plugSDK. init ({\\n3 // Please ensure you replace the app_id with your unique app id\\n4 app_id : \"\" ,\\n5 });\\n6 }, []);\\n\\nYou should now have PLuG chat widget installed on your website. Facing some issues? Reach out to us through our own PLuG chat widget from the bottom right of your screen.\\n\\nOnce the widget is installed on your website, every user who visits your website is considered an anonymous user. Anonymous users are the", - "title": "Install PLuG chat on your website" + "id": "ART-2893_KNOWLEDGE_NODE-2", + "text": "2| type=\"text/javascript\" \\n 3| src=\"https://plug-platform.devrev.ai/static/plug.js\" \\n 4| >\\n[/code] \\n \\nPlace the following code in the `` section of your HTML page:\\n\\n[code]\\n\\n 1| \\n[/code] \\n \\nThe PLuG widget should now be installed on", + "title": "Install the Web SDK \u2014 DevRev | Docs" }, { - "id": "ART-2059_KNOWLEDGE_NODE-0", - "text": "b'Product Platform Solutions Marketplace Company Resources Pricing\\n\\nLogin Book a demo\\nProduct Platform Solutions Marketplace Company Resources Pricing\\nLogin Book a demo\\nSearch CTRL + K\\n\\nIntroduction AgentOS platform\\n\\nCore concepts Apps Groups Parts & trails Vistas Vista Reports\\nTasks Updates Customer email notifications Roles Default privileges by group\\nAccess control Object customization Glossary Search People insights Workflow Templates Accessing DevRev External identity provider", + "id": "ART-2059_KNOWLEDGE_NODE-7", + "text": "these steps.\\n\\nIn DevRev, go to Settings. > Support. > PLuG Settings. through the settings icon in the top-left corner.\\nClick Enable PLuG Widget. if it isn\\'t already enabled.\\nCopy your Unique App ID. from the Configuration tab..\\nSetup for HTML.\\n\\nPlace this code in the head of your HTML page.\\n\\n1 //\\n2 < script\\n3 type = \"text/javascript\"\\n4 src = \"https://plug-platform.devrev.ai/static/plug.js\"\\n5 > \\n\\nPlace this code in the body of your HTML page.\\n\\n1 < script >\\n2", "title": "Install PLuG chat on your website" }, { - "id": "ART-2059_KNOWLEDGE_NODE-3", - "text": "status change Slack notifier Slash commands Smart sprint Spam Shield Ticket age in engineering Work duration\\n\\nIntegrate\\n\\nBitbucket Calendly Datadog Google Calendar Email Slack WhatsApp GitHub Harness Marker.io Instabug Qase Twilio Glean SendSafely\\n\\nAirdrop\\n\\nHubspot Airdrop Salesforce Airdrop Zendesk Airdrop Freshdesk Airdrop Rocketlane Airdrop Confluence Airdrop ServiceNow Airdrop Jira Airdrop DevRev for Jira app\\nLinear Airdrop ClickUp Airdrop Azure Boards Airdrop\\n\\nPLuG\\n\\nInstall", - "title": "Install PLuG chat on your website" + "id": "ART-15490_KNOWLEDGE_NODE-1", + "text": "code snippet provided below on every page where you want the widget to appear for website visitors.\\n\\nUnique app ID\\n-------------\\n\\nEnsure to replace the app ID with your app ID which identifies your Plug search widget. You can access your app ID from your DevRev account by following these steps.\\n\\n1. In DevRev, go to **Settings** > **Support** > **Plug Settings** through the settings icon in the top-left corner.\\n2. Click **Enable Plug Widget** if it isn\\xe2\\x80\\x99t already enabled.\\n3.", + "title": "Install Plug search | DevRev | Docs" }, { - "id": "ART-2894_KNOWLEDGE_NODE-1", - "text": "__\\n\\n[Pricing](https://devrev.ai/pricing)\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](https://devrev.ai/request-a-demo)\\n\\nOn this page\\n\\n * [Unique app ID](/public/sdks/web/install-search#unique-app-id)\\n * [Bind a hotkey to toggle search agent](/public/sdks/web/install-search#bind-a-hotkey-to-toggle-search-agent)\\n\\n[SDKs](/public/sdks)[PLuG Web SDK](/public/sdks/web/installation)\\n\\n#\\n\\nInstall PLuG search\\n\\nTo get the PLuG search widget to appear on your website and web app,", - "title": "Install PLuG search \u2014 DevRev | Docs" + "id": "ART-1270_KNOWLEDGE_NODE-3", + "text": "might get a warning message from window.plugSDK.init() being called multiple times. These errors won\\xe2\\x80\\x99t impact the installation and functioning of the widget.\\n\\nInitialize search.\\n\\nCalling the initSearchAgent() method initializes the PLuG Search agent on your website. Initializing search is necessary for you to perform any other actions on the PLuG widget SDK.\\n\\n1 useEffect ( () => { 2 window. plugSDK. init ( { 3 app_id : \\' \\' , 4 disable_plug_chat_window :", + "title": "Methods \u2014 DevRev | Docs" }, { - "id": "ART-2059_KNOWLEDGE_NODE-8", - "text": "window.plugSDK.init({\\n3 // Please ensure you replace the app_id with your unique app id\\n4 app_id: \"\",\\n5 });\\n6 \\nSetup for React.\\n\\nPlace this in public/index.html file, inside the body tag of your HTML page.\\n\\n1 ;\\n\\nPlace this code inside the react component where you want to render the chat widget. Typically you should do it as top level component like", - "title": "Install PLuG chat on your website" + "id": "ART-2897_KNOWLEDGE_NODE-18", + "text": "search agent on your website. This initialization is required before performing any other actions with the PLuG widget SDK.\\n\\n[code]\\n\\n 1| useEffect(() => { \\n ---|--- \\n 2| window.plugSDK.init({ \\n 3| app_id: \\'\\', \\n 4| disable_plug_chat_window: true, \\n 5| }); \\n 6| \\n 7| window.plugSDK.onEvent((payload) => { \\n 8| if (payload.type === \\'ON_PLUG_WIDGET_READY\\') { \\n 9| window.plugSDK.initSearchAgent(); \\n", + "title": "Methods \u2014 DevRev | Docs" + }, + { + "id": "ART-1944_KNOWLEDGE_NODE-4", + "text": "PLuG chat on your website Install PLuG search on your website Identify your users with PLuG Customize Nudges SDK\\n\\nChangelog\\n\\nSeptember 01 to September 30 August 01 to August 31 July 01 to July 31, 2024 June 01 to June 28, 2024 May 01 to May 31, 2024 April 01 to April 29, 2024 Mar 01 to Mar 29, 2024 Feb 10 to Feb 29, 2024 Jan 09, 2024 to Feb 09, 2024 Dec 08, 2023 to Jan 08, 2024 Nov 10 to Dec 07, 2023 Oct 13 to Nov 09, 2023 Sep 15 to Oct 12, 2023 Aug 17 to Sep 14, 2023 Jul 20 to Aug 16, 2023", + "title": "DevRev Documentation" } ] }, @@ -3475,55 +3475,55 @@ "query_id": "80fd3cb8-b4ff-4ca4-8d4b-2b0ac1fdab5b", "query": "send notification to slack when a ticket is manually assigned", "retrievals": [ - { - "id": "ART-2017_KNOWLEDGE_NODE-28", - "text": "you would like to tag on the message (the ticket owner gets tagged automatically); and the target Slack channel. The channel\\'s ID can be found by going to the channel details. Refer to the placeholder value on the input to see an example of how this looks.\\n2. Decide if notifications should go out even if the ticket has a target end date set. Set the toggle to the desired behavior.\\n3. Decide if a ticket should pass the check if it\\'s part is a descendant of the filter part. For example, if a", - "title": "SLA status change Slack notifier | Automate | Snap-ins | DevRev" - }, { "id": "ART-2035_KNOWLEDGE_NODE-42", "text": "ticket notifications\\n\\n* Enable through the **Notify on new ticket creation** snap-in configuration.\\n* Provide a Slack channel ID in the **Channel ID to send ticket notifications** configuration.\\n* Snap-in will send notifications to the target channel whenever a new ticket is created, regardless of the source channel or platform.\\n* Notification message threads are **not** synced between platforms.\\n\\n### Notifications for ticket state update\\n\\n* Enable through **Notify on ticket state", "title": "Slack | Integrate | Snap-ins | DevRev" }, { - "id": "ART-2017_KNOWLEDGE_NODE-25", - "text": "ticket\\'s owner and subscribers, when a ticket\\'s resolution time SLA changes into the *Warning* or *Breached* stage.\\n\\n![]()\\n\\nFor more information, refer to the\\n[SLA status change Slack notifier snap-in](/marketplace/sla-status-change-slack-notifier) on the DevRev\\nmarketplace.\\n\\nInstallation\\n------------\\n\\n1. Create a Slack app for your workspace in .\\n2. In App features, generate bot token in **OAuth & Permissions**.\\n3. Grant the app bot the following", - "title": "SLA status change Slack notifier | Automate | Snap-ins | DevRev" + "id": "ART-2035_KNOWLEDGE_NODE-38", + "text": "recommended if you already have a conversation in progress. Configure the snap-in to send or not send a ticket summary card to the Slack thread using the **Notify on conversation to ticket conversion** setting. Regardless, the Slack thread will sync with the new ticket instead of the ongoing conversation.\\n\\n![]()\\n\\nSlack does not support slash commands in threads.\\n\\nChoosing one of the first two options will open a pop-up modal with the new ticket form. Complete the required fields; some", + "title": "Slack | Integrate | Snap-ins | DevRev" }, { - "id": "ART-2035_KNOWLEDGE_NODE-36", - "text": "Slack Channel ID in the **Channel ID to send conversation notifications** snap-in configuration as the target to post notifications.\\n\\n* Any new message within tickets in the customer messages panel is also subjected to the same automation.\\n* To prevent notification overload, each conversation or ticket is subject to a five minute cooldown period between notifications. Multiple consecutive messages within this window will not trigger additional notifications.\\n* Notification threads are not", + "id": "ART-2035_KNOWLEDGE_NODE-43", + "text": "update** snap-in configuration.\\n* Applies only to tickets syncing with Slack threads.\\n* If enabled, the Slack snap-in will send notifications to the syncing thread whenever the ticket state changes.\\n\\n### Ticket digest\\n\\nTo see all open and in-progress tickets in Slack, use the /devrev ticket-digest command. This opens a modal with a paginated list of all open and in-progress tickets.\\n\\nDevRev Issues and Slack\\n-----------------------\\n\\nThe Slack snap-in allows issues to be created", "title": "Slack | Integrate | Snap-ins | DevRev" }, { - "id": "ART-2912_KNOWLEDGE_NODE-13", - "text": "group](/docs/automations/set-user-preference)\\n - [SLA status change Slack notifier](/docs/automations/sla-change-notifier)\\n - [Slash commands](/docs/automations/slash-commands)\\n - [Spam Shield](/docs/automations/spam-shield)\\n - [Subtype Migration](/docs/automations/subtype-migration)\\n - [Ticket age in engineering](/docs/automations/ticket-age-in-engineering)\\n - [Ticket issue field migrator](/docs/automations/ticket-issue-field-migrator)\\n - [Ticket", - "title": "Ticket email notifier | Automate | Snap-ins | DevRev" + "id": "ART-2017_KNOWLEDGE_NODE-27", + "text": "Connection**.\\n * Select **Slack** from the dowpdown list.\\n * Give it a name and sign in with Slack. Ensure to toggle on **Make public** to make the connection public for your organization.\\n\\nConfigure the snap-in\\n---------------------\\n\\n1. In the **Configuration** tab, the first input field to set is *filters*. Here you can declare for which tickets to track the SLA status and to which channels to send notifications.\\n\\n Set the ticket subtype, severity, and part; the support heads", + "title": "SLA status change Slack notifier | Automate | Snap-ins | DevRev" }, { - "id": "ART-2017_KNOWLEDGE_NODE-29", - "text": "ticket with part set as \"Feature 1\" should trigger a notification when the filter is set to \"Capability 1\" and this is a parent part of that feature. Set the toggle to the desired behavior.\\n4. Check the default message body and change it if you would like a different phrasing.\\n\\n[PreviousSet user preference for group](/docs/automations/set-user-preference)[NextSlash commands](/docs/automations/slash-commands)\\n\\n#### On this page\\n\\n* [Installation](#installation)\\n* [Configure the", + "id": "ART-2017_KNOWLEDGE_NODE-25", + "text": "ticket\\'s owner and subscribers, when a ticket\\'s resolution time SLA changes into the *Warning* or *Breached* stage.\\n\\n![]()\\n\\nFor more information, refer to the\\n[SLA status change Slack notifier snap-in](/marketplace/sla-status-change-slack-notifier) on the DevRev\\nmarketplace.\\n\\nInstallation\\n------------\\n\\n1. Create a Slack app for your workspace in .\\n2. In App features, generate bot token in **OAuth & Permissions**.\\n3. Grant the app bot the following", "title": "SLA status change Slack notifier | Automate | Snap-ins | DevRev" }, { - "id": "ART-2017_KNOWLEDGE_NODE-27", - "text": "Connection**.\\n * Select **Slack** from the dowpdown list.\\n * Give it a name and sign in with Slack. Ensure to toggle on **Make public** to make the connection public for your organization.\\n\\nConfigure the snap-in\\n---------------------\\n\\n1. In the **Configuration** tab, the first input field to set is *filters*. Here you can declare for which tickets to track the SLA status and to which channels to send notifications.\\n\\n Set the ticket subtype, severity, and part; the support heads", + "id": "ART-2017_KNOWLEDGE_NODE-28", + "text": "you would like to tag on the message (the ticket owner gets tagged automatically); and the target Slack channel. The channel\\'s ID can be found by going to the channel details. Refer to the placeholder value on the input to see an example of how this looks.\\n2. Decide if notifications should go out even if the ticket has a target end date set. Set the toggle to the desired behavior.\\n3. Decide if a ticket should pass the check if it\\'s part is a descendant of the filter part. For example, if a", "title": "SLA status change Slack notifier | Automate | Snap-ins | DevRev" }, { - "id": "ART-2035_KNOWLEDGE_NODE-38", - "text": "recommended if you already have a conversation in progress. Configure the snap-in to send or not send a ticket summary card to the Slack thread using the **Notify on conversation to ticket conversion** setting. Regardless, the Slack thread will sync with the new ticket instead of the ongoing conversation.\\n\\n![]()\\n\\nSlack does not support slash commands in threads.\\n\\nChoosing one of the first two options will open a pop-up modal with the new ticket form. Complete the required fields; some", + "id": "ART-2035_KNOWLEDGE_NODE-36", + "text": "Slack Channel ID in the **Channel ID to send conversation notifications** snap-in configuration as the target to post notifications.\\n\\n* Any new message within tickets in the customer messages panel is also subjected to the same automation.\\n* To prevent notification overload, each conversation or ticket is subject to a five minute cooldown period between notifications. Multiple consecutive messages within this window will not trigger additional notifications.\\n* Notification threads are not", "title": "Slack | Integrate | Snap-ins | DevRev" }, { - "id": "ART-2017_KNOWLEDGE_NODE-24", - "text": "[Product demos](/docs/DevRevU/demos)\\n\\nOn this page\\n\\n* [Installation](#installation)\\n* [Configure the snap-in](#configure-the-snapin)\\n\\n1. [Documentation](/docs)\\n3. [Snap-ins](/docs/snapins)\\n[Automate](/docs/automate)\\n[SLA status change Slack notifier](/docs/automations/sla-change-notifier)\\n\\nSLA status change Slack notifier\\n================================\\n\\nGet alerted on your ticket\\'s SLAs. This snap-in sends a notification through Slack to user configured channels, tagging the", - "title": "SLA status change Slack notifier | Automate | Snap-ins | DevRev" + "id": "ART-2035_KNOWLEDGE_NODE-25", + "text": "Tickets](#followup-and-merged-tickets)\\n* [New ticket notifications](#new-ticket-notifications)\\n* [Notifications for ticket state update](#notifications-for-ticket-state-update)\\n* [Ticket digest](#ticket-digest)\\n* [DevRev Issues and Slack](#devrev-issues-and-slack)\\n* [DevRev Incidents and Slack](#devrev-incidents-and-slack)\\n* [Sync options](#sync-options)\\n* [Share and view record details](#share-and-view-record-details)\\n* [Creating custom workflows](#creating-custom-workflows)\\n*", + "title": "Slack | Integrate | Snap-ins | DevRev" }, { - "id": "ART-2017_KNOWLEDGE_NODE-13", - "text": "creator](/docs/automations/smart-issue-creator)\\n - [Set user preference for group](/docs/automations/set-user-preference)\\n - [SLA status change Slack notifier](/docs/automations/sla-change-notifier)\\n - [Slash commands](/docs/automations/slash-commands)\\n - [Spam Shield](/docs/automations/spam-shield)\\n - [Subtype Migration](/docs/automations/subtype-migration)\\n - [Ticket age in engineering](/docs/automations/ticket-age-in-engineering)\\n - [Ticket issue field", - "title": "SLA status change Slack notifier | Automate | Snap-ins | DevRev" + "id": "ART-2035_KNOWLEDGE_NODE-48", + "text": "channel.\\n\\n1. **Sync messages with the thread (for incidents created from Slack)**\\n\\n* Works only for incidents created from Slack.\\n* It syncs messages with the originating thread, similar to ticket and issue work items.\\n\\n1. **Sync messages with the notification thread**\\n\\n* Syncs with the thread of the incident notification sent on the channel mentioned in the **Channel ID to send incident notifications** configuration.\\n* Works for all incidents irrespective of source channel or", + "title": "Slack | Integrate | Snap-ins | DevRev" + }, + { + "id": "ART-4199_KNOWLEDGE_NODE-28", + "text": "**Trigger URL** that is displayed.\\n6. Paste the Trigger URL under **Enable Events** in the custom Slack bot.\\n\\n[PreviousTicket linked issues comment sync](/docs/automations/ticket-linked-issues-comment-sync)[NextIntegrate](/docs/integrate)\\n\\n#### On this page\\n\\n* [Install](#install)\\n* [Configure the custom Slack bot](#configure-the-custom-slack-bot)\\n* [Configure DevRev](#configure-devrev)\\n\\n[Enterprise grade security to protect customer data\\n\\nLearn more about", + "title": "Slack message agent | Automate | Snap-ins | DevRev" } ] }, @@ -3532,54 +3532,54 @@ "query": "export all accounts without 500 limit", "retrievals": [ { - "id": "ART-1255_KNOWLEDGE_NODE-8", - "text": "Many Requests Error\\n\\n500\\n\\nInternal Server Error\\n\\n503\\n\\nService Unavailable Error\\n\\nWas this page helpful?\\n\\nYesNo\\n\\n[Previous](/api-reference/accounts/export)[#### Get Account\\n\\nNext](/api-reference/accounts/get)[Built with](https://buildwithfern.com/?utm_campaign=buildWith&utm_medium=docs&utm_source=developer.devrev.ai)'", - "title": "Export Accounts (POST) | DevRev | Docs" + "id": "ART-1254_KNOWLEDGE_NODE-0", + "text": "b'Export Accounts | DevRev | Docs\\n\\n[![]()![]()](https://developer.devrev.ai/)\\n\\nPublic\\n\\nPublic\\n\\nSearch\\n\\n`/`\\n\\n[API Reference](/api-reference/getting-started)[accounts](/api-reference/accounts/accounts)\\n\\nExport Accounts\\n===============\\n\\nCopy page\\n\\nGET\\n\\nhttps://api.devrev.ai/accounts.export\\n\\nGET\\n\\n/accounts.export\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl https://api.devrev.ai/accounts.export \\\\ |\\n| > | -H \"Authorization: Bearer \" |\\n```\\n\\n[Try", + "title": "Export Accounts | DevRev | Docs" }, { - "id": "ART-1462_KNOWLEDGE_NODE-3", - "text": "Error\\n\\n500\\n\\nInternal Server Error\\n\\n503\\n\\nService Unavailable Error\\n\\nPOST\\n\\n/accounts.export\\n\\n[code]\\n\\n $| curl -X POST https://api.devrev.ai/accounts.export \\\\ \\n ---|--- \\n >| -H \"Authorization: Bearer \" \\\\ \\n >| -H \"Content-Type: application/json\" \\\\ \\n >| -d \\'{}\\'\\n[/code] \\n \\nTry it\\n\\n200accountsExportPostExample\\n\\n[code]\\n\\n 1| { \\n ---|--- \\n 2| \"accounts\": [ \\n 3| { \\n 4| \"id\": \"foo\", \\n 5|", - "title": "Export Accounts (POST) \u2014 DevRev | Docs" + "id": "ART-1303_KNOWLEDGE_NODE-6", + "text": "exported accounts.\\nShow 18 properties\\nGET / accounts.export\\n$ curl -G https://api.devrev.ai/accounts.export \\\\ > -H \" Authorization: Bearer \" \\\\ > --data-urlencode created_date.after=2023-01-01T12:00:00Z \\\\ > --data-urlencode created_date.before=2023-01-01T12:00:00Z \\\\ > --data-urlencode modified_date.after=2023-01-01T12:00:00Z \\\\ > --data-urlencode modified_date.before=2023-01-01T12:00:00Z\\n200 Retrieved 1 { 2 \" accounts \" : [ 3 { 4 \" created_date \" : \" 2023-01-01T12:00:00Z \" , 5 \"", + "title": "Export Post \u2014 DevRev | Docs" }, { - "id": "ART-1254_KNOWLEDGE_NODE-9", - "text": "Export Accounts (POST)\\n\\nNext](/api-reference/accounts/export-post)[Built with](https://buildwithfern.com/?utm_campaign=buildWith&utm_medium=docs&utm_source=developer.devrev.ai)'", - "title": "Export Accounts | DevRev | Docs" + "id": "ART-1449_KNOWLEDGE_NODE-4", + "text": "specified stages.\\n\\ntierlist of stringsOptional\\n\\nTier of the accounts to be filtered.\\n\\nwebsiteslist of stringsOptional\\n\\nArray of websites of accounts to be filtered.\\n\\n### Response\\n\\nThe response to exporting a collection of accounts.\\n\\naccountslist of objects\\n\\nThe exported accounts.\\n\\nShow 14 properties\\n\\n### Errors\\n\\n400\\n\\nBad Request Error\\n\\n401\\n\\nUnauthorized Error\\n\\n403\\n\\nForbidden Error\\n\\n429\\n\\nToo Many Requests Error\\n\\n500\\n\\nInternal Server Error\\n\\n503\\n\\nService", + "title": "Export Accounts \u2014 DevRev | Docs" }, { - "id": "ART-1254_KNOWLEDGE_NODE-1", - "text": "it](/api-reference/accounts/export?explorer=true)\\n\\n200Retrieved\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | { |\\n| 2 | \"accounts\": [ |\\n| 3 | { |\\n| 4 | \"id\": \"string\", |\\n| 5 | \"owned_by\": [ |\\n| 6 | { |\\n| 7 | \"display_id\": \"string\", |\\n| 8 | \"id\": \"string\", |\\n| 9 | \"display_name\": \"string\", |\\n| 10 | \"display_picture\": { |\\n| 11 | \"display_id\": \"string\", |\\n| 12 | \"id\": \"string\", |\\n| 13 | \"file\": { |\\n| 14 | \"type\": \"string\", |\\n| 15 | \"name\": \"string\", |\\n| 16 | \"size\": 1 |\\n| 17 | } |\\n| 18", - "title": "Export Accounts | DevRev | Docs" + "id": "ART-1255_KNOWLEDGE_NODE-1", + "text": "|\\n| > | -H \"Content-Type: application/json\" \\\\ |\\n| > | -d \\'{}\\' |\\n```\\n\\n[Try it](/api-reference/accounts/export-post?explorer=true)\\n\\n200Successful\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | { |\\n| 2 | \"accounts\": [ |\\n| 3 | { |\\n| 4 | \"id\": \"string\", |\\n| 5 | \"owned_by\": [ |\\n| 6 | { |\\n| 7 | \"display_id\": \"string\", |\\n| 8 | \"id\": \"string\", |\\n| 9 | \"display_name\": \"string\", |\\n| 10 | \"display_picture\": { |\\n| 11 | \"display_id\": \"string\", |\\n| 12 | \"id\": \"string\", |\\n| 13 | \"file\": { |\\n| 14", + "title": "Export Accounts (POST) | DevRev | Docs" }, { - "id": "ART-1255_KNOWLEDGE_NODE-1", - "text": "|\\n| > | -H \"Content-Type: application/json\" \\\\ |\\n| > | -d \\'{}\\' |\\n```\\n\\n[Try it](/api-reference/accounts/export-post?explorer=true)\\n\\n200Successful\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | { |\\n| 2 | \"accounts\": [ |\\n| 3 | { |\\n| 4 | \"id\": \"string\", |\\n| 5 | \"owned_by\": [ |\\n| 6 | { |\\n| 7 | \"display_id\": \"string\", |\\n| 8 | \"id\": \"string\", |\\n| 9 | \"display_name\": \"string\", |\\n| 10 | \"display_picture\": { |\\n| 11 | \"display_id\": \"string\", |\\n| 12 | \"id\": \"string\", |\\n| 13 | \"file\": { |\\n| 14", + "id": "ART-1255_KNOWLEDGE_NODE-0", + "text": "b'Export Accounts (POST) | DevRev | Docs\\n\\n[![]()![]()](https://developer.devrev.ai/)\\n\\nPublic\\n\\nPublic\\n\\nSearch\\n\\n`/`\\n\\n[API Reference](/api-reference/getting-started)[accounts](/api-reference/accounts/accounts)\\n\\nExport Accounts (POST)\\n======================\\n\\nCopy page\\n\\nPOST\\n\\nhttps://api.devrev.ai/accounts.export\\n\\nPOST\\n\\n/accounts.export\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl -X POST https://api.devrev.ai/accounts.export \\\\ |\\n| > | -H \"Authorization: Bearer \" \\\\", "title": "Export Accounts (POST) | DevRev | Docs" }, { - "id": "ART-1254_KNOWLEDGE_NODE-0", - "text": "b'Export Accounts | DevRev | Docs\\n\\n[![]()![]()](https://developer.devrev.ai/)\\n\\nPublic\\n\\nPublic\\n\\nSearch\\n\\n`/`\\n\\n[API Reference](/api-reference/getting-started)[accounts](/api-reference/accounts/accounts)\\n\\nExport Accounts\\n===============\\n\\nCopy page\\n\\nGET\\n\\nhttps://api.devrev.ai/accounts.export\\n\\nGET\\n\\n/accounts.export\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl https://api.devrev.ai/accounts.export \\\\ |\\n| > | -H \"Authorization: Bearer \" |\\n```\\n\\n[Try", + "id": "ART-1254_KNOWLEDGE_NODE-1", + "text": "it](/api-reference/accounts/export?explorer=true)\\n\\n200Retrieved\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | { |\\n| 2 | \"accounts\": [ |\\n| 3 | { |\\n| 4 | \"id\": \"string\", |\\n| 5 | \"owned_by\": [ |\\n| 6 | { |\\n| 7 | \"display_id\": \"string\", |\\n| 8 | \"id\": \"string\", |\\n| 9 | \"display_name\": \"string\", |\\n| 10 | \"display_picture\": { |\\n| 11 | \"display_id\": \"string\", |\\n| 12 | \"id\": \"string\", |\\n| 13 | \"file\": { |\\n| 14 | \"type\": \"string\", |\\n| 15 | \"name\": \"string\", |\\n| 16 | \"size\": 1 |\\n| 17 | } |\\n| 18", "title": "Export Accounts | DevRev | Docs" }, { - "id": "ART-1255_KNOWLEDGE_NODE-0", - "text": "b'Export Accounts (POST) | DevRev | Docs\\n\\n[![]()![]()](https://developer.devrev.ai/)\\n\\nPublic\\n\\nPublic\\n\\nSearch\\n\\n`/`\\n\\n[API Reference](/api-reference/getting-started)[accounts](/api-reference/accounts/accounts)\\n\\nExport Accounts (POST)\\n======================\\n\\nCopy page\\n\\nPOST\\n\\nhttps://api.devrev.ai/accounts.export\\n\\nPOST\\n\\n/accounts.export\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl -X POST https://api.devrev.ai/accounts.export \\\\ |\\n| > | -H \"Authorization: Bearer \" \\\\", - "title": "Export Accounts (POST) | DevRev | Docs" + "id": "ART-1826_KNOWLEDGE_NODE-6", + "text": "exported accounts.\\nShow 18 properties\\nAPI Reference accounts Export Post.\\n\\nPOST https:// api.devrev.ai / accounts.export\\nExports a collection of accounts.\\nRequest.\\n\\nThis endpoint expects an object.\\ncreated_by list of strings Optional\\nFilters for accounts created by the specified user(s).\\ncreated_date object Optional\\nShow 2 properties\\ncustom_fields map from strings to any Optional\\nFilters for custom fields.\\ndisplay_name list of strings Optional\\nArray of display names of accounts", + "title": "Get Post \u2014 DevRev | Docs" }, { - "id": "ART-1449_KNOWLEDGE_NODE-5", - "text": "Unavailable Error\\n\\nGET\\n\\n/accounts.export\\n\\n[code]\\n\\n $| curl https://api.devrev.ai/accounts.export \\\\ \\n ---|--- \\n >| -H \"Authorization: Bearer \"\\n[/code] \\n \\nTry it\\n\\n200exportExample\\n\\n[code]\\n\\n 1| { \\n ---|--- \\n 2| \"accounts\": [ \\n 3| { \\n 4| \"id\": \"foo\", \\n 5| \"owned_by\": [ \\n 6| { \\n 7| \"display_id\": \"foo\", \\n 8| \"id\": \"foo\", \\n 9| \"display_name\": \"foo\", \\n", - "title": "Export Accounts \u2014 DevRev | Docs" + "id": "ART-1803_KNOWLEDGE_NODE-6", + "text": "exported accounts.\\nShow 18 properties\\nAPI Reference accounts Export Post.\\n\\nPOST https:// api.devrev.ai / accounts.export\\nExports a collection of accounts.\\nRequest.\\n\\nThis endpoint expects an object.\\ncreated_by list of strings Optional\\nFilters for accounts created by the specified user(s).\\ncreated_date object Optional\\nShow 2 properties\\ncustom_fields map from strings to any Optional\\nFilters for custom fields.\\ndisplay_name list of strings Optional\\nArray of display names of accounts", + "title": "List \u2014 DevRev | Docs" }, { - "id": "ART-1254_KNOWLEDGE_NODE-8", - "text": "stringsOptional\\n\\nArray of websites of accounts to be filtered.\\n\\n### Response\\n\\nThe response to exporting a collection of accounts.\\n\\naccountslist of objects\\n\\nThe exported accounts.\\n\\nShow 14 properties\\n\\n### Errors\\n\\n400\\n\\nBad Request Error\\n\\n401\\n\\nUnauthorized Error\\n\\n403\\n\\nForbidden Error\\n\\n429\\n\\nToo Many Requests Error\\n\\n500\\n\\nInternal Server Error\\n\\n503\\n\\nService Unavailable Error\\n\\nWas this page helpful?\\n\\nYesNo\\n\\n[Previous](/api-reference/accounts/delete)[####", - "title": "Export Accounts | DevRev | Docs" + "id": "ART-1304_KNOWLEDGE_NODE-6", + "text": "exported accounts.\\nShow 18 properties\\nAPI Reference accounts Export Post.\\n\\nPOST https:// api.devrev.ai / accounts.export\\nExports a collection of accounts.\\nRequest.\\n\\nThis endpoint expects an object.\\ncreated_by list of strings Optional\\nFilters for accounts created by the specified user(s).\\ncreated_date object Optional\\nShow 2 properties\\ncustom_fields map from strings to any Optional\\nFilters for custom fields.\\ndisplay_name list of strings Optional\\nArray of display names of accounts", + "title": "Get \u2014 DevRev | Docs" }, { - "id": "ART-1449_KNOWLEDGE_NODE-1", - "text": "__\\n\\n[Pricing](https://devrev.ai/pricing)\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](https://devrev.ai/request-a-demo)\\n\\n[API Reference](/public/api-reference/getting-started)[Accounts](/public/api-reference/accounts/accounts)\\n\\n# Export Accounts\\n\\nGET\\n\\nhttps://api.devrev.ai/accounts.export\\n\\nTry it\\n\\nExports a collection of accounts.\\n\\n### Query parameters\\n\\ncreated_bylist of stringsOptional\\n\\nFilters for accounts created by the specified", - "title": "Export Accounts \u2014 DevRev | Docs" + "id": "ART-1605_KNOWLEDGE_NODE-6", + "text": "exported accounts.\\nShow 18 properties\\nAPI Reference accounts Export Post.\\n\\nPOST https:// api.devrev.ai / accounts.export\\nExports a collection of accounts.\\nRequest.\\n\\nThis endpoint expects an object.\\ncreated_by list of strings Optional\\nFilters for accounts created by the specified user(s).\\ncreated_date object Optional\\nShow 2 properties\\ncustom_fields map from strings to any Optional\\nFilters for custom fields.\\ndisplay_name list of strings Optional\\nArray of display names of accounts", + "title": "Create \u2014 DevRev | Docs" } ] }, @@ -3588,54 +3588,54 @@ "query": "export report CSV download location", "retrievals": [ { - "id": "ART-1254_KNOWLEDGE_NODE-1", - "text": "it](/api-reference/accounts/export?explorer=true)\\n\\n200Retrieved\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | { |\\n| 2 | \"accounts\": [ |\\n| 3 | { |\\n| 4 | \"id\": \"string\", |\\n| 5 | \"owned_by\": [ |\\n| 6 | { |\\n| 7 | \"display_id\": \"string\", |\\n| 8 | \"id\": \"string\", |\\n| 9 | \"display_name\": \"string\", |\\n| 10 | \"display_picture\": { |\\n| 11 | \"display_id\": \"string\", |\\n| 12 | \"id\": \"string\", |\\n| 13 | \"file\": { |\\n| 14 | \"type\": \"string\", |\\n| 15 | \"name\": \"string\", |\\n| 16 | \"size\": 1 |\\n| 17 | } |\\n| 18", - "title": "Export Accounts | DevRev | Docs" + "id": "ART-16355_KNOWLEDGE_NODE-24", + "text": "CSV](#validations-for-uploading-csv)\\n* [Upload commands from CSV](#upload-commands-from-csv)\\n\\n1. [Documentation](/docs)\\n3. [Snap-ins](/docs/snapins)\\n[Automate](/docs/automate)\\n[CSV commands uploader](/docs/automations/csv-commands-uploader)\\n\\nCSV commands uploader\\n=====================\\n\\nThe CSV commands uploader is a snap-in designed to streamline the process of creating commands for work items in bulk through a CSV file. It efficiently handles commands while providing dynamic error", + "title": "CSV commands uploader | Automate | Snap-ins | DevRev" }, { - "id": "ART-1449_KNOWLEDGE_NODE-0", - "text": "b'[](/public/api-reference/accounts/export)\\n\\nPublic\\n\\n[](https://devrev.ai)\\n\\n * Product\\n * Platform\\n * Solutions\\n * Marketplace\\n * Company\\n * Resources\\n * [Pricing](https://devrev.ai/pricing)\\n\\n __\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](https://devrev.ai/request-a-demo)\\n\\n[](https://devrev.ai)\\n\\n __\\n\\nProduct __\\n\\nPlatform __\\n\\nSolutions __\\n\\nMarketplace __\\n\\nCompany __\\n\\nResources", - "title": "Export Accounts \u2014 DevRev | Docs" + "id": "ART-2575_KNOWLEDGE_NODE-32", + "text": "required headers | Include headers for the required fields in the CSV. |\\n\\n[PreviousContacts](/docs/product/customers)[NextGrow snap-ins](/docs/product/snapins-grow)\\n\\n#### On this page\\n\\n* [Import data](#import-data)\\n* [CSV file requirements](#csv-file-requirements)\\n* [Mandatory fields](#mandatory-fields)\\n* [Array fields](#array-fields)\\n* [Tags](#tags)\\n* [Owner fields](#owner-fields)\\n* [Limitations](#limitations)\\n* [Troubleshooting](#troubleshooting)\\n\\n[Enterprise grade security to", + "title": "Account and contact import | Computer for Growth Teams | DevRev" }, { - "id": "ART-1244_KNOWLEDGE_NODE-1", - "text": "it](/api-reference/works/export?explorer=true)\\n\\n200Retrieved\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | { |\\n| 2 | \"works\": [ |\\n| 3 | { |\\n| 4 | \"created_by\": { |\\n| 5 | \"display_id\": \"string\", |\\n| 6 | \"id\": \"string\", |\\n| 7 | \"display_name\": \"string\", |\\n| 8 | \"display_picture\": { |\\n| 9 | \"display_id\": \"string\", |\\n| 10 | \"id\": \"string\", |\\n| 11 | \"file\": { |\\n| 12 | \"type\": \"string\", |\\n| 13 | \"name\": \"string\", |\\n| 14 | \"size\": 1 |\\n| 15 | } |\\n| 16 | }, |\\n| 17 | \"email\": \"string\", |\\n| 18", - "title": "Export Works | DevRev | Docs" + "id": "ART-16355_KNOWLEDGE_NODE-31", + "text": "is completed, a sample CSV is generated in the **Discussion** tab of the snap-in with the status of the operation, including each line number, any error messages for failed rows, and the display ID of the created commands for successful rows.\\n9. In case of a retry, a command timeline entry is created, and the user needs to re-enter the command /upload\\\\_commands .\\n\\n[PreviousCSV comments uploader](/docs/automations/csv-comments-uploader)[NextDescope identity", + "title": "CSV commands uploader | Automate | Snap-ins | DevRev" }, { - "id": "ART-1254_KNOWLEDGE_NODE-0", - "text": "b'Export Accounts | DevRev | Docs\\n\\n[![]()![]()](https://developer.devrev.ai/)\\n\\nPublic\\n\\nPublic\\n\\nSearch\\n\\n`/`\\n\\n[API Reference](/api-reference/getting-started)[accounts](/api-reference/accounts/accounts)\\n\\nExport Accounts\\n===============\\n\\nCopy page\\n\\nGET\\n\\nhttps://api.devrev.ai/accounts.export\\n\\nGET\\n\\n/accounts.export\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl https://api.devrev.ai/accounts.export \\\\ |\\n| > | -H \"Authorization: Bearer \" |\\n```\\n\\n[Try", - "title": "Export Accounts | DevRev | Docs" + "id": "ART-15689_KNOWLEDGE_NODE-24", + "text": "CSV](#validations-for-uploading-csv)\\n* [Upload comments from CSV on work-items](#upload-comments-from-csv-on-workitems)\\n\\n1. [Documentation](/docs)\\n3. [Snap-ins](/docs/snapins)\\n[Automate](/docs/automate)\\n[CSV comments uploader](/docs/automations/csv-comments-uploader)\\n\\nCSV comments uploader\\n=====================\\n\\nThe CSV comments uploader is a snap-in designed to streamline the process of creating timeline entries on work items in bulk through a CSV file. It efficiently handles", + "title": "CSV comments uploader | Automate | Snap-ins | DevRev" }, { - "id": "ART-1449_KNOWLEDGE_NODE-10", - "text": "\"modified_date\": \"2023-01-01T12:00:00.000Z\", \\n 69| \"primary_account\": { \\n 70| \"id\": \"foo\", \\n 71| \"display_id\": \"foo\", \\n 72| \"display_name\": \"foo\" \\n 73| }, \\n 74| \"tier\": \"foo\", \\n 75| \"websites\": [ \\n 76| \"foo\" \\n 77| ] \\n 78| } \\n 79| ] \\n 80| }\\n[/code] \\n \\n[Export Accounts (POST)Up Next](/public/api-reference/accounts/export-post)\\n\\n[Built", - "title": "Export Accounts \u2014 DevRev | Docs" + "id": "ART-2017_KNOWLEDGE_NODE-11", + "text": "uploader](/docs/automations/csv-work-item-uploader)\\n - [CSV comments uploader](/docs/automations/csv-comments-uploader)\\n - [CSV commands uploader](/docs/automations/csv-commands-uploader)\\n - [Descope identity validation](/docs/automations/descope-identity-validation)\\n - [Effort logger](/docs/automations/effort-logger)\\n - [HTTP archive file upload & sanitization](/docs/automations/har-sanitization)\\n - [Link preview](/docs/automations/link-preview)\\n - [Org tags", + "title": "SLA status change Slack notifier | Automate | Snap-ins | DevRev" }, { - "id": "ART-1254_KNOWLEDGE_NODE-9", - "text": "Export Accounts (POST)\\n\\nNext](/api-reference/accounts/export-post)[Built with](https://buildwithfern.com/?utm_campaign=buildWith&utm_medium=docs&utm_source=developer.devrev.ai)'", - "title": "Export Accounts | DevRev | Docs" + "id": "ART-4186_KNOWLEDGE_NODE-11", + "text": "uploader](/docs/automations/csv-work-item-uploader)\\n - [CSV comments uploader](/docs/automations/csv-comments-uploader)\\n - [CSV commands uploader](/docs/automations/csv-commands-uploader)\\n - [Descope identity validation](/docs/automations/descope-identity-validation)\\n - [Effort logger](/docs/automations/effort-logger)\\n - [HTTP archive file upload & sanitization](/docs/automations/har-sanitization)\\n - [Link preview](/docs/automations/link-preview)\\n - [Org tags", + "title": "Computer for User Insights | Session analytics | Computer for Your Customers | DevRev" }, { - "id": "ART-1302_KNOWLEDGE_NODE-11", - "text": "accounts.export\\n$ curl -G https://api.devrev.ai/accounts.export \\\\ > -H \" Authorization: Bearer \" \\\\ > --data-urlencode created_date.after=2023-01-01T12:00:00Z \\\\ > --data-urlencode created_date.before=2023-01-01T12:00:00Z \\\\ > --data-urlencode modified_date.after=2023-01-01T12:00:00Z \\\\ > --data-urlencode modified_date.before=2023-01-01T12:00:00Z\\n200 Retrieved 1 { 2 \" accounts \" : [ 3 { 4 \" created_date \" : \" 2023-01-01T12:00:00Z \" , 5 \" display_id \" : \" display_id \" , 6 \" id \" : \"", - "title": "Export \u2014 DevRev | Docs" + "id": "ART-2575_KNOWLEDGE_NODE-11", + "text": "uploader](/docs/automations/csv-work-item-uploader)\\n - [CSV comments uploader](/docs/automations/csv-comments-uploader)\\n - [CSV commands uploader](/docs/automations/csv-commands-uploader)\\n - [Descope identity validation](/docs/automations/descope-identity-validation)\\n - [Effort logger](/docs/automations/effort-logger)\\n - [HTTP archive file upload & sanitization](/docs/automations/har-sanitization)\\n - [Link preview](/docs/automations/link-preview)\\n - [Org tags", + "title": "Account and contact import | Computer for Growth Teams | DevRev" }, { - "id": "ART-1449_KNOWLEDGE_NODE-5", - "text": "Unavailable Error\\n\\nGET\\n\\n/accounts.export\\n\\n[code]\\n\\n $| curl https://api.devrev.ai/accounts.export \\\\ \\n ---|--- \\n >| -H \"Authorization: Bearer \"\\n[/code] \\n \\nTry it\\n\\n200exportExample\\n\\n[code]\\n\\n 1| { \\n ---|--- \\n 2| \"accounts\": [ \\n 3| { \\n 4| \"id\": \"foo\", \\n 5| \"owned_by\": [ \\n 6| { \\n 7| \"display_id\": \"foo\", \\n 8| \"id\": \"foo\", \\n 9| \"display_name\": \"foo\", \\n", - "title": "Export Accounts \u2014 DevRev | Docs" + "id": "ART-6174_KNOWLEDGE_NODE-11", + "text": "uploader](/docs/automations/csv-work-item-uploader)\\n - [CSV comments uploader](/docs/automations/csv-comments-uploader)\\n - [CSV commands uploader](/docs/automations/csv-commands-uploader)\\n - [Descope identity validation](/docs/automations/descope-identity-validation)\\n - [Effort logger](/docs/automations/effort-logger)\\n - [HTTP archive file upload & sanitization](/docs/automations/har-sanitization)\\n - [Link preview](/docs/automations/link-preview)\\n - [Org tags", + "title": "Conversation to ticket conversion | Conversations | Computer for Support Teams | DevRev" }, { - "id": "ART-1255_KNOWLEDGE_NODE-0", - "text": "b'Export Accounts (POST) | DevRev | Docs\\n\\n[![]()![]()](https://developer.devrev.ai/)\\n\\nPublic\\n\\nPublic\\n\\nSearch\\n\\n`/`\\n\\n[API Reference](/api-reference/getting-started)[accounts](/api-reference/accounts/accounts)\\n\\nExport Accounts (POST)\\n======================\\n\\nCopy page\\n\\nPOST\\n\\nhttps://api.devrev.ai/accounts.export\\n\\nPOST\\n\\n/accounts.export\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl -X POST https://api.devrev.ai/accounts.export \\\\ |\\n| > | -H \"Authorization: Bearer \" \\\\", - "title": "Export Accounts (POST) | DevRev | Docs" + "id": "ART-15689_KNOWLEDGE_NODE-29", + "text": "invalid headers and any missing required headers.\\n7. After the operation is completed, a sample CSV is generated in the **Discussion** tab of the snap-in with the status of the operation, including each line number, any error messages for failed rows, and the link of the successfully created timeline entry for successful rows.\\n8. In case of a retry, a timeline entry is created, and the user needs to re-enter the command /upload\\\\_timelines.\\n\\n[PreviousCSV work item", + "title": "CSV comments uploader | Automate | Snap-ins | DevRev" }, { - "id": "ART-1255_KNOWLEDGE_NODE-1", - "text": "|\\n| > | -H \"Content-Type: application/json\" \\\\ |\\n| > | -d \\'{}\\' |\\n```\\n\\n[Try it](/api-reference/accounts/export-post?explorer=true)\\n\\n200Successful\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | { |\\n| 2 | \"accounts\": [ |\\n| 3 | { |\\n| 4 | \"id\": \"string\", |\\n| 5 | \"owned_by\": [ |\\n| 6 | { |\\n| 7 | \"display_id\": \"string\", |\\n| 8 | \"id\": \"string\", |\\n| 9 | \"display_name\": \"string\", |\\n| 10 | \"display_picture\": { |\\n| 11 | \"display_id\": \"string\", |\\n| 12 | \"id\": \"string\", |\\n| 13 | \"file\": { |\\n| 14", - "title": "Export Accounts (POST) | DevRev | Docs" + "id": "ART-16355_KNOWLEDGE_NODE-26", + "text": "**Reported\\\\_by,** and **Contact** columns, provide the email of the person to be assigned as the owner or reporter of the work item. If the CSV lists multiple owners, only the first will be set as the owner.\\n* For the **Applies to Part**, **Stage**, **Account**, **Developed with Parts**, and **Tags** columns, provide the part name, stage name, account name, part name, and tag name respectively as it is present in the UI, ensuring case sensitivity.\\n* For **Date** and **Timestamp** related", + "title": "CSV commands uploader | Automate | Snap-ins | DevRev" } ] }, @@ -3644,54 +3644,54 @@ "query": "ticket calls show playback access issue", "retrievals": [ { - "id": "ART-1447_KNOWLEDGE_NODE-8", - "text": "demo](https://devrev.ai/request-a-demo)\\n\\n'", - "title": "Tickets and issues \u2014 DevRev | Docs" + "id": "ART-1483_KNOWLEDGE_NODE-18", + "text": "the code\\n\\nUpdate the code in `src/functions/ticket_creator/index.ts` to reflect the behavior.\\n\\nFirstly, import the DevRev TypeScript SDK in the `index.ts` file\\n\\nindex.ts\\n\\n[code]\\n\\n 1| import {client, publicSDK} from \"@devrev/typescript-sdk\"; \\n ---|---\\n[/code] \\n \\nNext, update the `run` function in the hello-world example. Since the ticket gets created frequently, set some creation time in the title and the body. The example uses the part as `PROD-1` and keeps the owner as", + "title": "Using a snap-in to perform a DevRev action \u2014 DevRev | Docs" }, { - "id": "ART-1979_KNOWLEDGE_NODE-41", - "text": "progress\\n\\n\\n\\nOpen\\n\\n\\n\\nEscalate\\n\\n\\n\\nValidate the fix\\n\\n\\n\\nAdditional detail needed\\n\\n\\n\\nCustomer responds\\n\\n\\n\\nStart\\n\\n\\n\\nFeature request accepted\\n\\n\\n\\nResolved\\n\\n\\n\\nNot valid\\n\\n\\n\\nQueued\\n\\n\\n\\nWork in progress\\n\\n\\n\\nAwaiting product assist\\n\\n\\n\\nAwaiting development\\n\\n\\n\\nAwating customer response\\n\\n\\n\\nIn development\\n\\n\\n\\nAccepted\\n\\n\\n\\nResolved\\n\\n\\n\\nCanceled\\n```\\n\\n**Open**\\n\\n* *Queued* (Q)\\n The initial stage for all tickets. When a new ticket is created,", - "title": "Tickets | Computer for Support Teams | DevRev" + "id": "ART-15701_KNOWLEDGE_NODE-9", + "text": "information.\\n\\nDevRev recommends to switch on both agent and customer recording and realtime and post call analytics.\\n\\nCapturing user input in IVR: If you are taking inputs from user in the IVR and you want that information to be visible to the agent/ captured in the call, use set contact attributes block. Store the keys in the User Defined Namespace and add the key which needs to be displayed/ captured. For eg: previous_ticket_id is being captured by the user input.\\n\\nAdd users: Navigate", + "title": "Amazon Connect Telephony Integration Guide" }, { - "id": "ART-1979_KNOWLEDGE_NODE-39", - "text": "other tickets or issues that relate to this ticket, click **Link Records** and select the relevant items.\\n7. If you would like to immediately create another ticket, select **Create multiple**.\\n8. Click **Create**.\\n\\nIf a ticket is created from an existing conversation, then the ticket's title and description are populated automatically from the conversation.\\n\\n![]()\\n\\nYou can create a child issue by clicking **+ Link issue** > **Add a child issue**. You can link the other existing issue as", - "title": "Tickets | Computer for Support Teams | DevRev" + "id": "ART-16803_KNOWLEDGE_NODE-26", + "text": "Tickets\\n* Meetings\\n* Objects linked to issues\\n* Users\\n\\nTo configure a workspace object loop:\\n\\n1. On the **workflow canvas**, add an action step named **Loop for [Object]**, where [Object] is the entity you want to iterate over.\\n2. Apply **filter conditions** to refine the set of objects included in the loop and perform operations on them.\\n\\nAll **actions** inside the loop execute once per object that satisfies the filter conditions.\\n\\n### For Each\\n\\nThe **For Each** loop iterates", + "title": "Workflow nodes | Workflows | Computer by DevRev | DevRev" }, { - "id": "ART-1002_KNOWLEDGE_NODE-1", - "text": "\\xe2\\x86\\x92 Issues\\n Items to track customer requests/problems \\xe2\\x86\\x92 Tickets\\n\\n\\nGiven the converged nature of the DevRev platform, we have both Tickets, and Issues, so when do you use what? The answer is \\xe2\\x80\\x9cit depends\\xe2\\x80\\x9d on what your role is on the part you\\xe2\\x80\\x99re creating the work item on. In general, issues should be restricted to those individuals that either own or contribute to a part. Tickets should be used for all customer/consumer (internal or", - "title": "Tickets, Issues: When to Use Each" + "id": "ART-15664_KNOWLEDGE_NODE-13", + "text": "\\n\\nYou may want to restrict links to specific subtypes of objects. For example, only allowing issues\\nof a particular subtype to be linked to tickets.\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl --location \\'https://api.devrev.ai/link-types.custom.create\\' \\\\ |\\n| > | --header \\'Content-Type: application/json\\' \\\\ |\\n| > | --header \\'Authorization: Bearer \\' \\\\ |\\n| > | --data \\'{ |\\n| > | \"name\": \"Link between social media issues and tickets\", |\\n| > | \"source_types\": [ |\\n| > | { |\\n|", + "title": "Links | DevRev | Docs" }, { - "id": "ART-1979_KNOWLEDGE_NODE-27", - "text": "also be used to engage customers for feedback/ideas (such as new feature ideas). Scoping is important for broadcast tickets as there needs to be a differentiation between broadcast (all revs) vs. multicast (particular revs).\\n\\nViews of tickets can be found under **Support** in the DevRev app.\\n\\n![]()\\n\\nYou can export views to CSV or JSON by selecting **Actions** in the upper-right corner and choosing the format.\\n\\nAttributes\\n----------\\n\\nTickets have attributes that can be used to filter", - "title": "Tickets | Computer for Support Teams | DevRev" + "id": "ART-2024_KNOWLEDGE_NODE-27", + "text": "help now... ask again in 5d\\n\\nSample response:\\n\\n> I am unable to assist you at the moment, however please reach out to me again in five days and I will be happy to help you.\\n\\n### Summarize\\n\\nUsing the summarize command, you can sum up the entire conversation. It applies to the following:\\n\\n* Conversation\\n* Tickets\\n* Issues\\n* Part\\n* Workspace\\n* Customer\\n* Account\\n\\nSample response:\\n\\n> **Summary:**\\n>\\n> * Rahul from DummyOrg is having difficulty installing the Plug Widget.\\n> *", + "title": "Slash commands | Automate | Snap-ins | DevRev" }, { - "id": "ART-1447_KNOWLEDGE_NODE-1", - "text": "[Tickets](https://docs.devrev.ai/product/tickets) and [Issues](https://docs.devrev.ai/product/issues).\\n\\nWas this page helpful?YesNo\\n\\n[Create WorkUp Next](/public/api-reference/works/create)\\n\\n[Built with](https://buildwithfern.com/?utm_campaign=buildWith&utm_medium=docs&utm_source=developer.devrev.ai)\\n\\n[Enterprise grade security to protect customer dataLearn more about it.](https://devrev.ai/blog/soc-compliance)\\n\\nProduct\\n\\n * [Build](https://devrev.ai/build)\\n *", - "title": "Tickets and issues \u2014 DevRev | Docs" + "id": "ART-1444_KNOWLEDGE_NODE-9", + "text": "breachedcompletedpausedrunningwarning\\n\\nticket.source_channellist of stringsOptional\\n\\nFilters for tickets with any of the provided source channels.\\n\\nticket.source_channel_v2list of stringsOptional\\n\\nFilters for tickets that are associated with any of the source channels.\\n\\ntypelist of enumsOptional\\n\\nFilters for work of the provided types.\\n\\nAllowed values: issueticket\\n\\n### Response\\n\\nSuccess.\\n\\nworkslist of objects\\n\\nThe list of works.\\n\\nShow 2", + "title": "List Works \u2014 DevRev | Docs" }, { - "id": "ART-15716_KNOWLEDGE_NODE-8", - "text": "for TicketsWe have a summarize option (it would resemble sparkle symbol) in the top right corner of the ticket view, which uses the ticket content to summarize the ticket\\n\\n7. Difference between Issues and Tickets\\n\\nTickets\\xc2\\xa0are for customer support\\xe2\\x80\\x94tracking requests, problems, or questions from customers or prospects.\\n\\nIssues\\xc2\\xa0are internal work items for developers\\xe2\\x80\\x94used to improve the product, fix bugs, or implement features. Issues can be linked to", - "title": "Support queries related playbook" + "id": "ART-1961_KNOWLEDGE_NODE-37", + "text": "\\n{{Ticket\\xc2\\xa0Created\\xc2\\xa0>\\xc2\\xa0Output\\xc2\\xa0>\\xc2\\xa0Reported\\xc2\\xa0By\\xc2\\xa0>\\xc2\\xa0Rev\\xc2\\xa0Org\\xc2\\xa0>\\xc2\\xa0Display\\xc2\\xa0Name}}.\\xe2\\x80\\x9d\\n\\n\\n\\nDelay\\n\\n\\n\\nDuration: 2 minutes\\n\\n\\n\\nIf-else\\n\\n\\n\\nAttribute:\\xc2\\xa0Ticket\\xc2\\xa0Created/Output\\xc2\\xa0>\\xc2\\xa0Applies\\xc2\\xa0to\\xc2\\xa0part\\xc2\\xa0>\\xc2\\xa0Display\\xc2\\xa0ID \\nOperator: Equals \\nOperand: CAPL-18\\n\\n\\n\\nTicket \\ncreated\\n\\n\\n\\nEnd\\n```\\n\\n[### Workflow action", + "title": "Workflows | Computer by DevRev | DevRev" }, { - "id": "ART-1002_KNOWLEDGE_NODE-3", - "text": "systems being used for engineering work are commonly abused by sales, marketing and support teams. For example, a sales rep may create an issue for a developer for a customer request. In the case of support, you\\xe2\\x80\\x99ll commonly see a ton of duplicate issues when only one was really necessary. This leads to a lot of noise for developers, and devalues the notion of an \\xe2\\x80\\x9cissue\\xe2\\x80\\x9d. By keeping a clear line between tickets and issues, we ensure the following:\\n\\n\\n issues", - "title": "Tickets, Issues: When to Use Each" + "id": "ART-1949_KNOWLEDGE_NODE-26", + "text": "upper-right corner after you make a change.\\n You can toggle on **Show groups** in **Group by** dropdown to open up a side panel showing the groups.\\n\\n![]()\\n\\n![]()\\n\\nYou can also apply **Actions** > **Smart Clustering** if the number of tickets or issues is under 10,000. Clustering isn't available for conversations.\\n\\n1. Click **Save as**. You can give the list a name, and description and save it which causes it to show up in the **My list** section at the bottom of the left-side nav", + "title": "Vistas | Computer by DevRev | DevRev" }, { - "id": "ART-1979_KNOWLEDGE_NODE-40", - "text": "a child issue or create a new one by clicking on **+ New issue**.\\nJust update the title of the child issue and click enter. All other fields will be populated automatically by DevRev. You can edit them later.\\n\\nTags\\n----\\n\\n* Stalled\\n* Priority/Escalated\\n* Fast/Slow Moving\\n* Blocked\\n* Resolution: [*value*]\\n* Impact: [*value*]\\n* Reason: [*value*]\\n\\nStages\\n------\\n\\nThe following figure shows the state machine for tickets.\\n\\n```\\nClosed\\n\\n\\n\\nIn", - "title": "Tickets | Computer for Support Teams | DevRev" + "id": "ART-16611_KNOWLEDGE_NODE-4", + "text": "ticket ID, issue ID)\\n // - value: array of attachments belonging to that parent\\n \\n for (const [parentId, attachments] of reducedAttachments) {\\n // Fetch the parent item to get fresh attachment URLs\\n // Implement your custom logic here (API call, URL refresh, token renewal, etc.)\\n const freshAttachments = await refetchParentAttachments(parentId);\\n \\n // Process each attachment in this parent group\\n for (const attachment of attachments) {\\n // Find the", + "title": "Using custom processors for attachments in Airdrop snap-in" }, { - "id": "ART-1242_KNOWLEDGE_NODE-0", - "text": "b'Tickets and issues | DevRev | Docs\\n\\n[![]()![]()](https://developer.devrev.ai/)\\n\\nPublic\\n\\nPublic\\n\\nSearch\\n\\n`/`\\n\\n[API Reference](/api-reference/getting-started)[works](/api-reference/works/tickets-and-issues)\\n\\nTickets and issues\\n==================\\n\\nCopy page\\n\\n`works` endpoint\\n\\n\\xe2\\x84\\xb9\\xef\\xb8\\x8f A work item is a record of some work that has to be done for a customer (ticket) or for another builder or maintainer of a part (issue).\\n\\n\\xf0\\x9f\\x93\\x8c For more information", - "title": "Tickets and issues | DevRev | Docs" + "id": "ART-1981_KNOWLEDGE_NODE-26", + "text": "a small number of tags to help categorize tickets. For example, at DevRev we have the following: bug, feature-request, other-request, question, and incident.\\n* Designate one or more customer experience engineers to be on call. Add them to the **Support** group inside **Settings > Groups** and as default owner in the **Support Routing** snap-in. Default owners are notified through email and the DevRev app as soon as a new conversation is started.\\n\\nMonitor the inbox\\n-----------------\\n\\n*", + "title": "Support best practices | Computer for Support Teams | DevRev" } ] }, @@ -3705,49 +3705,49 @@ "title": "Issues with Salesforce OAuth connection" }, { - "id": "ART-2047_KNOWLEDGE_NODE-30", - "text": "it\\'s your first).\\n2. Create a new connection to your Salesforce account, or use an existing connection if you already have one.\\n3. Once the connection is established, select the Salesforce account you want to import and specify the DevRev part that should be used for any imported cases without a product. This initiates a bulk import of the selected account.\\n4. DevRev makes an effort to automatically map the fields from Salesforce to corresponding fields in DevRev. However, you may be", - "title": "Salesforce AirSync | AirSync | Snap-ins | DevRev" + "id": "ART-4057_KNOWLEDGE_NODE-3", + "text": "Error\\n\\n401\\n\\nUnauthorized Error\\n\\n403\\n\\nForbidden Error\\n\\n429\\n\\nToo Many Requests Error\\n\\n500\\n\\nInternal Server Error\\n\\n503\\n\\nService Unavailable Error\\n\\nPOST\\n\\n/dev-orgs.auth-connections.list\\n\\n[code]\\n\\n $| curl -X POST https://api.devrev.ai/dev-orgs.auth-connections.list \\\\ \\n ---|--- \\n >| -H \"Authorization: Bearer \" \\\\ \\n >| -H \"Content-Type: application/json\" \\\\ \\n >| -d \\'{}\\'\\n[/code] \\n \\nTry", + "title": "List Dev Orgs Auth Connections (POST) \u2014 DevRev | Docs" }, { - "id": "ART-15716_KNOWLEDGE_NODE-3", - "text": "SMTP/IMAP). You\\xe2\\x80\\x99ll need admin access to complete the setup.\\n\\n[Email integration setup instructions](https://devrev.ai/docs/integrations/email)\\n\\n6. Syncing Cases Between DevRev and Salesforce\\n\\nYes, you can sync cases (tickets) from DevRev to Salesforce using the Salesforce integration. Mapping and sync options are available during setup.\\n\\n[Syncing cases with Salesforce](https://devrev.ai/docs/integrations/salesforce#sync-cases)\\n\\n7. Supported Airdrop Sources\\n\\nDevRev Airdrop", - "title": "Support queries related playbook" + "id": "ART-4056_KNOWLEDGE_NODE-3", + "text": "Error\\n\\n500\\n\\nInternal Server Error\\n\\n503\\n\\nService Unavailable Error\\n\\nGET\\n\\n/dev-orgs.auth-connections.get\\n\\n[code]\\n\\n $| curl -G https://api.devrev.ai/dev-orgs.auth-connections.get \\\\ \\n ---|--- \\n >| -H \"Authorization: Bearer \" \\\\ \\n >| -d id=id\\n[/code] \\n \\nTry it\\n\\n200devOrgAuthConnectionsGetExample\\n\\n[code]\\n\\n 1| { \\n ---|--- \\n 2| \"auth_connection\": {} \\n 3| }\\n[/code] \\n \\n[Get Dev Orgs Auth Connection (POST)Up", + "title": "Get Dev Orgs Auth Connection \u2014 DevRev | Docs" }, { - "id": "ART-2047_KNOWLEDGE_NODE-36", - "text": "DevRev**.\\n\\n![]()\\n\\nThis may override fields in previously imported items, even if they were modified in DevRev.\\n\\n### Sync to Salesforce\\n\\nAfter a successful import from a Salesforce account, you can sync changes made in DevRev to the previously imported cases back to Salesforce. Additionally, any new [DevRev tickets marked for sync](#mark-a-devrev-ticket-for-syncing) is created as new Salesforce items.\\n\\nTo perform a one-time sync to Salesforce, follow these steps:\\n\\n1. Go to", - "title": "Salesforce AirSync | AirSync | Snap-ins | DevRev" + "id": "ART-4055_KNOWLEDGE_NODE-2", + "text": "Error\\n\\n500\\n\\nInternal Server Error\\n\\n503\\n\\nService Unavailable Error\\n\\nPOST\\n\\n/dev-orgs.auth-connections.get\\n\\n[code]\\n\\n $| curl -X POST https://api.devrev.ai/dev-orgs.auth-connections.get \\\\ \\n ---|--- \\n >| -H \"Authorization: Bearer \" \\\\ \\n >| -H \"Content-Type: application/json\" \\\\ \\n >| -d \\'{ \\n >| \"id\": \"foo\" \\n >| }\\'\\n[/code] \\n \\nTry it\\n\\n200authConnectionsDevOrgAuthConnectionsGetPostExample\\n\\n[code]\\n\\n 1| { \\n", + "title": "Get Dev Orgs Auth Connection (POST) \u2014 DevRev | Docs" }, { - "id": "ART-2047_KNOWLEDGE_NODE-35", - "text": "longer available.\\n\\n### Sync to DevRev\\n\\nAfter a successful import from a Salesforce account, you can choose to sync the imported data with DevRev. This feature airdrops any new items and any changes made to previously imported items from Salesforce.\\n\\nTo perform a one-time sync to DevRev, follow these steps:\\n\\n1. Go to **Settings** > **Integrations** > **AirSyncs**.\\n2. Locate the previously imported project.\\n3. Select **\\xe2\\x8b\\xae** > **Sync Salesforce Service to", - "title": "Salesforce AirSync | AirSync | Snap-ins | DevRev" + "id": "ART-15360_KNOWLEDGE_NODE-3", + "text": "Error\\n\\n429\\n\\nToo Many Requests Error\\n\\n500\\n\\nInternal Server Error\\n\\n503\\n\\nService Unavailable Error\\n\\nWas this page helpful?\\n\\nYesNo\\n\\n[Previous](/api-reference/auth-connections/dev-org-auth-connections-create)[#### Get Dev Orgs Auth Connection\\n\\nNext](/api-reference/auth-connections/dev-org-auth-connections-get)[Built with](https://buildwithfern.com/?utm_campaign=buildWith&utm_medium=docs&utm_source=developer.devrev.ai)'", + "title": "Delete Dev Orgs Auth Connection | DevRev | Docs" }, { - "id": "ART-17569_KNOWLEDGE_NODE-2", - "text": "connection:\\n\\nOpen a Support Case w/ SFDC Support.\\n\\nAsk to have the API Access Control feature enabled\\n\\nOnce enabled, go to the system user in SFDC and select the appropriate profle/permission set and go to System Permissions.\\n\\nCheck the box that says \"Use Any API client\"\\n\\nThis is a setting that wouldn\\'t be available without the API Access Control feature.\\n\\nRetry creating the connection after you\\'ve completed the previous steps.'", - "title": "Issues with Salesforce OAuth connection" + "id": "ART-15374_KNOWLEDGE_NODE-3", + "text": "Error\\n\\n429\\n\\nToo Many Requests Error\\n\\n500\\n\\nInternal Server Error\\n\\n503\\n\\nService Unavailable Error\\n\\nWas this page helpful?\\n\\nYesNo\\n\\n[Previous](/api-reference/auth-connections/dev-org-auth-connections-list-post)[#### Update Dev Orgs Auth Connection\\n\\nNext](/api-reference/auth-connections/dev-org-auth-connections-update)[Built with](https://buildwithfern.com/?utm_campaign=buildWith&utm_medium=docs&utm_source=developer.devrev.ai)'", + "title": "Toggle Dev Orgs Auth Connections | DevRev | Docs" }, { - "id": "ART-15716_KNOWLEDGE_NODE-2", - "text": "details](https://devrev.ai/docs/integrations/jira)\\n\\n4. Integration with Salesforce\\n\\nYes, DevRev offers a Salesforce integration. You can sync accounts, contacts, opportunities, and more between DevRev and Salesforce.\\n\\n[Salesforce integration overview](https://devrev.ai/docs/integrations/salesforce)\\n\\n5. Configuring Email Integration Snap-In\\n\\nGo to Settings \\xe2\\x86\\x92 Integrations \\xe2\\x86\\x92 Email, then follow the prompts to connect your email provider (Gmail, Outlook, or custom", - "title": "Support queries related playbook" + "id": "ART-1197_KNOWLEDGE_NODE-4", + "text": "\"urn:devrev:params:oauth:token-type:aat\", |\\n| 45 | \"scopes\": [ |\\n| 46 | \"string\" |\\n| 47 | ], |\\n| 48 | \"status\": \"active\", |\\n| 49 | \"subject\": \"string\", |\\n| 50 | \"token_hint\": \"string\" |\\n| 51 | } |\\n| 52 | } |\\n```\\n\\nGets the token metadata corresponding to the given token ID under the\\ngiven Dev organization.\\n\\n### Headers\\n\\nAuthorizationstringRequired\\n\\nBearer authentication of the form `Bearer `, where token is your auth token.\\n\\n### Request\\n\\nThis endpoint expects an", + "title": "Get Auth Token (POST) | DevRev | Docs" }, { - "id": "ART-16740_KNOWLEDGE_NODE-1", - "text": "expected sync is from DevRev \\xe2\\x86\\x92 Salesforce, the Owner field in Salesforce will be overwritten with the Owner value from DevRev.'", - "title": "Handling Conflicts in Two-Way Sync Between DevRev and External Systems" + "id": "ART-1371_KNOWLEDGE_NODE-10", + "text": "an error while authenticating the APIs? Refer to our [errors guide](/public/about/errors) to learn more about our error codes.\\n\\n## Next steps\\n\\nYou\\xe2\\x80\\x99re all set to explore our platform. You are ready to browse through our APIs and build your first integration with DevRev.\\n\\nWas this page helpful?YesNo\\n\\n[AttachmentsUp Next](/public/api-reference/artifacts/attachments)\\n\\n[Built", + "title": "Getting started \u2014 DevRev | Docs" }, { - "id": "ART-2047_KNOWLEDGE_NODE-37", - "text": "**Settings** > **Integrations** > **AirSyncs**.\\n2. Locate the previously imported project.\\n3. Select **\\xe2\\x8b\\xae** > **Sync DevRev to Salesforce Service**.\\n\\n![]()\\n\\nThis may override fields in Salesforce of previously imported items, even if they were modified in Salesforce.\\n\\n#### Mark a DevRev ticket for syncing\\n\\nUsing the [Sync to Salesforce](#sync-to-salesforce) feature, it\\'s possible to sync DevRev tickets to Salesforce. In order to sync a DevRev ticket to a specific Salesforce", - "title": "Salesforce AirSync | AirSync | Snap-ins | DevRev" + "id": "ART-1966_KNOWLEDGE_NODE-44", + "text": "errors**: Verify the sign\\\\_in\\\\_endpoint (SAML) or issuer (OIDC) is accessible and returns valid responses.\\n2. **Login failures**: Check that users are assigned to the application in your identity provider.\\n\\nFor additional support, contact the DevRev customer success team with your connection details and error messages.\\n\\n[PreviousAccessing DevRev](/docs/product/ui)[NextRemote MCP server](/docs/product/remote-mcp)\\n\\n#### On this page\\n\\n* [Before you begin](#before-you-begin)\\n* [Setup", + "title": "External identity provider setup | Computer by DevRev | DevRev" }, { - "id": "ART-2047_KNOWLEDGE_NODE-33", - "text": "Salesforce](#sync-to-salesforce):\\n + This option synchronizes any changes made in DevRev to previously synced Salesforce [supported items](#supported-objects) back to Salesforce. It also creates any [items marked in DevRev](#mark-a-devrev-ticket-for-syncing) for creation in Salesforce. This is a one-time operation.\\n* [Periodic Sync](#periodic-sync):\\n + By enabling this option, you can automatically sync new changes from Salesforce to DevRev on a periodic basis. The default frequency is", - "title": "Salesforce AirSync | AirSync | Snap-ins | DevRev" + "id": "ART-16805_KNOWLEDGE_NODE-37", + "text": "deleted, all the content it created gets deleted, even if they were modified in DevRev. It's possible to import the learning data again after its deletion.\\n\\nTo delete an import and all the content it created, go to **Settings > Integrations > Imports**, find the previously imported project, and select \\xe2\\x8b\\xae > **Delete Import**.\\n\\n### Limitations\\n\\n* Limited to API key authentication only; OAuth 2.0 not currently supported by Articulate Reach 360 platform.\\n* No delta synchronization", + "title": "Articulate Reach 360 AirSync | AirSync | Snap-ins | DevRev" } ] }, @@ -3756,54 +3756,54 @@ "query": "DevRev statistical data on ticket resolution time and customer benefits", "retrievals": [ { - "id": "ART-1975_KNOWLEDGE_NODE-25", - "text": "insights\\n===============\\n\\n* **Tickets created**\\n\\n The number of tickets created within the date range that meet the other filtering criteria.\\n* **Active tickets**\\n\\n The number of tickets that are in the Open or In Progress state.\\n* **Closed tickets**\\n\\n The number of tickets closed within the date range that meet the other filtering criteria.\\n* **Average resolution time**\\n\\n The average time taken to resolve tickets.\\n* **Median resolution time**\\n\\n The median time taken to", - "title": "Ticket insights | Support analytics | Computer for Support Teams | DevRev" + "id": "ART-1870_KNOWLEDGE_NODE-14", + "text": "customer ticket resolution times by 50%.\\n\\nFaster follow-up responses\\n\\nWith DevRev, ActionIQ has achieved a 60% reduction in turnaround time for responses to customer tickets.\\n\\nIncreased agent productivity\\n\\nImproved organization of work items, combined with workflow automation through Snap-Ins, drove a 68% increase in the number of incidents closed within Level 1 Support (per agent, per month) and an overall 18% increase in the number of incidents closed (per agent, per month).\\n\\n###", + "title": "Unifying teams: How ActionIQ transformed support with integration" }, { - "id": "ART-15792_KNOWLEDGE_NODE-8", - "text": "they come from - chat, email, Slack, phone - using unified data from across your company.\\n\\nCustomizable Ticket Routing: Route tickets with customizable workflows. Go beyond just priority and agent skill levels to assign the right ticket to the right person\\n\\nTakes actions: Support resolves common customer requests like password resets, subscription changes, and more from start to finish.\\n\\nUnified Data View: Eliminate disjointed middleware and layers of complex integrations. Speed up", - "title": "DevRev Products and Agents" + "id": "ART-1771_KNOWLEDGE_NODE-10", + "text": "approach to customer service. The result was faster responses, more accurate solutions, and a significantly improved customer experience.\\n\\nThe bottom line: A transformation in support operations\\n-------------------------------------------------------\\n\\nToughTrucksForKids\\' implementation of DevRev delivers concrete business results:\\n\\n* 64% reduction in ticket resolution time\\n* 83% improvement in first response time\\n* 30% increase in CSAT scores\\n* 20% increase in conversion rates\\n* 65%", + "title": "ToughTrucksForKids.com achieves dramatic efficiency gains and customer satisfaction through AI-powered support automation" }, { - "id": "ART-1975_KNOWLEDGE_NODE-28", - "text": "conversations against standalone tickets.\\n* **Tickets linked to issues**\\n\\n The percentage of tickets linked to product issues.\\n* **Active tickets by owner**\\n\\n The number of Open or In Progress tickets grouped by owner.\\n* **Tickets created vs. closed**\\n\\n The trend of tickets created against those closed.\\n\\nCustomer satisfaction (CSAT)\\n----------------------------\\n\\n* **CSAT score distribution**\\n\\n A distribution of customer satisfaction scores on tickets.\\n\\nTime spent per", - "title": "Ticket insights | Support analytics | Computer for Support Teams | DevRev" + "id": "ART-16570_KNOWLEDGE_NODE-13", + "text": "and improve, making information access increasingly effortless over time.\\n\\nData-backed transformation\\n--------------------------\\n\\nSince the rollout in June 2025, the data shows clear improvements in operational efficiency:\\n\\n* **+10 hrs saved** every user each week\\n* **~40% faster ticket resolution** when DevRev is used\\n* **Up to 75% faster resolution** in specific cases\\n* **Consistent adoption** across the team through June and July\\n\\nBenefits\\n--------\\n\\nFAME\\'s adoption of", + "title": "FAME transforms information access with AI-powered enterprise search" }, { - "id": "ART-1975_KNOWLEDGE_NODE-24", - "text": "[Product demos](/docs/DevRevU/demos)\\n\\nOn this page\\n\\n* [Customer & product impact](#customer-product-impact)\\n* [Ticket distribution](#ticket-distribution)\\n* [Customer satisfaction (CSAT)](#customer-satisfaction-csat)\\n* [Time spent per stage](#time-spent-per-stage)\\n\\n1. [Documentation](/docs)\\n3. [Computer for Support Teams](/docs/product/support)\\n[Support analytics](/docs/product/support-analytics)\\n[Ticket insights](/docs/dashboards/ticket-insights)\\n\\nTicket", - "title": "Ticket insights | Support analytics | Computer for Support Teams | DevRev" + "id": "ART-16189_KNOWLEDGE_NODE-13", + "text": "faster ticket resolution\\n* 57% drop in resolution time\\n* Improved coordination between support and engineering\\n* Real-time visibility into issue status\\n* Automation of routine support tasks\\n* Reduced backlog by 100+ tickets\\n* Enhanced customer communication and transparency\\n* Scalable, future-proof support operations\\n\\n### Related Articles\\n\\n[![]()\\n\\n5 min readLuxCreo boosts operational efficiency and agility with DevRev](/case-study/luxcreo)[![]()\\n\\n5 min readAditya Birla Capital", + "title": "FOSSA\u2019s Unified Support Strategy for Elevated Customer Experience" }, { - "id": "ART-1977_KNOWLEDGE_NODE-26", - "text": "owner.\\n* **Average Resolution Time**\\n\\n Average time taken to resolve tickets by ticket owners.\\n\\n[PreviousTicket-SLA Analytics](/docs/dashboards/ticket-sla-analytics)[NextConversations](/docs/product/conversation)\\n\\n[Enterprise grade security to protect customer data\\n\\nLearn more about it.\\n\\n![]()](/blog/soc-compliance)\\n\\nComputer\\n\\n* [Meet Computer](/meet-computer)\\n* [How Computer works](/how-computer-works)\\n\\nApps\\n\\n* [For Support Teams](/for-support-teams)\\n* [For", - "title": "Ticket-Team Performance | Support analytics | Computer for Support Teams | DevRev" + "id": "ART-2749_KNOWLEDGE_NODE-7", + "text": "impact: Enhanced collaboration, faster resolution, measurable results\\n-------------------------------------------------------------------------\\n\\n### Improved support operations\\n\\nPhenom's adoption of Computer by DevRev has significantly improved support operations by allowing L1 and L2 teams to collaborate within the same tool, leading to a 30% decrease in ticket resolution time and a 29% decrease in time to close tickets.\\n\\nCustomer self-service options were improved with Computer CX", + "title": "Phenom transforms talent experience with streamlined support and development workflows" }, { - "id": "ART-1975_KNOWLEDGE_NODE-27", - "text": "customer satisfaction score for tickets.\\n* **Escalated tickets**\\n\\n The number of tickets that are escalated.\\n\\nCustomer & product impact\\n-------------------------\\n\\n* **Active tickets by customer**\\n\\n The number of Open or In Progress tickets grouped by customer.\\n* **Active tickets by part**\\n\\n The number of Open or In Progress tickets grouped by part.\\n\\nTicket distribution\\n-------------------\\n\\n* **Tickets linked to conversations**\\n\\n The percentage of tickets linked from", - "title": "Ticket insights | Support analytics | Computer for Support Teams | DevRev" + "id": "ART-1870_KNOWLEDGE_NODE-10", + "text": "retention or engagement\\n\\n![]()\\n\\nTasso ArgyrosCEO, ActionIQ\\n\\nThe bottom line: Transforming support through connected operations\\n------------------------------------------------------------------\\n\\nActionIQ's implementation of DevRev delivered concrete business results:\\n\\n* 67% reduction in median incident resolution times\\n* 50% faster customer ticket resolution\\n* 60% reduction in turnaround time for responses to customer tickets\\n* 68% increase in incidents closed within Level 1", + "title": "Unifying teams: How ActionIQ transformed support with integration" }, { - "id": "ART-1975_KNOWLEDGE_NODE-29", - "text": "stage\\n--------------------\\n\\n* **Average time spent per stage**\\n\\n The average time tickets spent in each stage.\\n\\n[PreviousConversation-Team Performance](/docs/dashboards/conversation-team-performance)[NextTicket-SLA Analytics](/docs/dashboards/ticket-sla-analytics)\\n\\n#### On this page\\n\\n* [Customer & product impact](#customer-product-impact)\\n* [Ticket distribution](#ticket-distribution)\\n* [Customer satisfaction (CSAT)](#customer-satisfaction-csat)\\n* [Time spent per", - "title": "Ticket insights | Support analytics | Computer for Support Teams | DevRev" + "id": "ART-17649_KNOWLEDGE_NODE-5", + "text": "helps the company deploy different PLuG instances across various website paths, each with its own appearance and memory.\\n\\n#### *DevRev's ticketing feature has really helped reduce escalations. Since we've set clear expectations that tickets will get responses within 24 to 48 hours, customers are more patient\\xe2\\x80\\x94unlike in chat, where they expect instant replies.*\\xe2\\x80\\x9d\\n\\n### Tailored knowledge management\\n\\nThe search agent accesses relevant information for each platform", + "title": "Leading APAC fintech transforms support with multi-instance AI solution" }, { - "id": "ART-1986_KNOWLEDGE_NODE-36", - "text": "conversations:\\n\\n**Tickets**\\n\\n| Metric | Default conditions | Start event | End event | Pause event | Resume event |\\n| --- | --- | --- | --- | --- | --- |\\n| First response time | * Ticket created by a customer * The ticket was created by a customer experience engineer but reported by a customer | Ticket created | * The agent added a comment to the customer chat * The ticket is moved to Awaiting Customer Response, or the ticket is closed | | |\\n| Next response time | * Ticket created by", - "title": "Service-level agreement | Computer for Support Teams | DevRev" + "id": "ART-2749_KNOWLEDGE_NODE-6", + "text": "tools, giving their support and engineering teams context on customer history, product usage, and prior interactions.\\n\\nThis shift improved operational efficiency while fostering better collaboration and faster resolution times, aligning more closely with Phenom's evolving needs and goals.\\n\\nWith DevRev, we've significantly reduced our ticket resolution time by 30%, enhancing our overall support efficiency.\\n\\n![]()\\n\\nMark MacDonaldVice President of Global Customer Care, Phenom\\n\\nThe", + "title": "Phenom transforms talent experience with streamlined support and development workflows" }, { - "id": "ART-1986_KNOWLEDGE_NODE-37", - "text": "a customer * The ticket was created by a customer experience engineer but reported by a customer | A new comment on the ticket by the customer after the customer experience engineer replied | * The agent added a comment to the customer chat * The ticket is moved to Awaiting Customer Response, or the ticket is closed | | |\\n| Full resolution time | * Ticket created by a customer * The ticket was created by a customer experience engineer but reported by a customer | Ticket created | The", - "title": "Service-level agreement | Computer for Support Teams | DevRev" + "id": "ART-1027_KNOWLEDGE_NODE-12", + "text": "driver\\n----------------------------------------------------------\\n\\nBy deploying DevRev, Descope has achieved:\\n\\n* 54% reduction in average resolution time\\n* 5\\xc3\\x97 faster ticket resolution with complete lifecycle visibility\\n* 300M+ users supported daily, up from 10M\\n* 100% SLA adherence maintained during scale\\n* 32\\xe2\\x80\\x9340% of inquiries resolved through AI-powered self-service\\n* Increased CSAT and reduced time to resolution\\n\\nThe result: a streamlined, product-led support", + "title": "Descope streamlines support at scale with automation, AI, and unified collaboration" }, { - "id": "ART-2662_KNOWLEDGE_NODE-4", - "text": "insights](/docs/dashboards/conversation-insights)\\n - [Conversation-SLA Analytics](/docs/dashboards/conversation-sla-analytics)\\n - [Conversation-Team Performance](/docs/dashboards/conversation-team-performance)\\n - [Ticket insights](/docs/dashboards/ticket-insights)\\n - [Ticket-SLA Analytics](/docs/dashboards/ticket-sla-analytics)\\n - [Ticket-Team Performance](/docs/dashboards/ticket-team-performance)\\n + [Conversations](/docs/product/conversation)\\n\\n - [Conversation to", - "title": "DevRev Documentation" + "id": "ART-4181_KNOWLEDGE_NODE-1", + "text": "context-aware, and customer-centric with SLAs that are connected to your customers, parts of your product, and issues - not just tickets.\\n\\nNever miss an SLA with DevRev\\n\\nReduction in SLA breaches\\n\\n40%\\n\\nImprovement in response time\\n\\n60%\\n\\nFaster ticket resolution\\n\\n4X\\n\\nEffortlessly create SLAs\\n========================\\n\\nSay goodbye to the hassle of creating SLAs using complex flowcharts\\n===================================================================\\n\\n[Read our", + "title": "Support like a lightning fast pit-crew" } ] }, @@ -3812,53 +3812,53 @@ "query": "who can provide access to a dashboard or board", "retrievals": [ { - "id": "ART-1958_KNOWLEDGE_NODE-30", - "text": "do not, by default, have permission to read any datasets besides their own. Admins are responsible for granting read permissions to all or a subset of datasets, which platform users can then utilize in building dashboards or reports.\\n\\n### Sharing\\n\\nThe share functionality allows dashboard or report editors to grant read or update permissions to other users.\\n\\n1. Select **Share** from the actions drop-down.\\n2. Search for the desired user, assign them a role (Editor or Viewer), then click", + "id": "ART-1958_KNOWLEDGE_NODE-28", + "text": "are not authorized to perform this action\". Relevant buttons may be inactive.\\nUsers can contact the organization\\'s admins to enable access in that case.\\n\\n![]()\\n\\nGranting access permissions\\n---------------------------\\n\\nUsers are granted access permissions to dashboards or reports through MFZ policies and sharing.\\n\\n### MFZ policies\\n\\nUse of MFZ policies facilitates the need to grant access to a wider group of users.\\n\\nAn org admin has permission to define and enable roles, in", "title": "Access control | Computer by DevRev | DevRev" }, { "id": "ART-1958_KNOWLEDGE_NODE-29", - "text": "whatever combination, that will give user groups permission to perform various operations on dashboards/reports. Out of the box, the following roles are enabled for the predefined user groups:\\n\\n* Admins\\n\\n ![]()\\n* Platform users\\n\\n ![]()\\n\\n By default, platform users have the following permissions:\\n\\n + Create dashboards or reports.\\n + Read, update, and delete their own dashboards or reports.\\n + Create datasets.\\n + Read, update, and delete their own datasets.\\n\\nPlatform users", + "text": "whatever combination, that will give user groups permission to perform various operations on dashboards/reports. Out of the box, the following roles are enabled for the predefined user groups:\\n\\n* Admins\\n\\n ![]()\\n* Platform users\\n\\n ![]()\\n\\n By default, platform users have the following permissions:\\n\\n + Create dashboards or reports.\\n + Read, update, and delete their own dashboards or reports.\\n + Create datasets.\\n + Read, update, and delete their own datasets.\\n\\nPlatform users", "title": "Access control | Computer by DevRev | DevRev" }, { - "id": "ART-1958_KNOWLEDGE_NODE-32", - "text": "**Create**: Build a dashboard or report. A user must have dashboard create permissions and dataset read permissions to create a dashboard or report.\\n* **Update**: Modify an existing dashboard or report. A user must have dashboard update permissions and dataset read permissions to modify a dashboard or report.\\n* **Share**: Allows a user to share an existing dashboard or report with other users. A user must have dashboard update permissions to share a dashboard or report.\\n\\n[PreviousDefault", - "title": "Access control | Computer by DevRev | DevRev" + "id": "ART-15687_KNOWLEDGE_NODE-31", + "text": "dashboards\\n-------------------\\n\\nDashboards organize and display multiple widgets.\\n\\n* **Access the dashboard builder**:\\n Similar to the widget builder, access the dashboard builder by modifying your DevRev workspace URL. For example, your\\\\_workspace\\\\_slug/dashboard-preview.\\n The builder provides a boilerplate code.\\n\\n ![]()\\n* **Link widgets to the dashboard**:\\n\\n + Scroll to the section that defines the widgets to be linked.\\n + Remove any existing widget IDs and paste the", + "title": "Dashboards | Computer by DevRev | DevRev" }, { - "id": "ART-1958_KNOWLEDGE_NODE-28", - "text": "are not authorized to perform this action\". Relevant buttons may be inactive.\\nUsers can contact the organization\\'s admins to enable access in that case.\\n\\n![]()\\n\\nGranting access permissions\\n---------------------------\\n\\nUsers are granted access permissions to dashboards or reports through MFZ policies and sharing.\\n\\n### MFZ policies\\n\\nUse of MFZ policies facilitates the need to grant access to a wider group of users.\\n\\nAn org admin has permission to define and enable roles, in", - "title": "Access control | Computer by DevRev | DevRev" + "id": "ART-15687_KNOWLEDGE_NODE-33", + "text": "organization.\\n Define the reference ID for each tab before mapping widgets to them.\\n* **Create the dashboard**:\\n Once satisfied with the linked widgets and layout, click the **Create dashboard** button.\\n* **Accessing dashboards**:\\n\\nSearch in the **Explore** section:\\n\\n* Go to **Explore** in the left nav in DevRev.\\n* Search for your dashboard by its name.\\n* Click on the dashboard to access it.\\n* For easy access, you can pin your dashboard under a section of your", + "title": "Dashboards | Computer by DevRev | DevRev" }, { - "id": "ART-1958_KNOWLEDGE_NODE-31", - "text": "**Share**.\\n\\nVista privileges\\n----------------\\n\\nTwo objects power vista reports: dashboards and datasets. Dashboards represent the view, while datasets represent the actual underlying data. A user must, at a minimum, have access permissions to dashboards in order to perform any meaningful operations on vista reports. Below is a list of possible operations:\\n\\n* **Read**: View a dashboard or report. Dashboard read permissions are required for a user to view a dashboard or report.\\n*", - "title": "Access control | Computer by DevRev | DevRev" + "id": "ART-13189_KNOWLEDGE_NODE-29", + "text": "and presentation needs.\\n + Share via Email: Dashboards can be directly shared via email, streamlining the process of distributing key metrics and insights to stakeholders.\\n\\n **What's improved:**\\n\\n + Enhanced Export Functionality: Improved the export functionality to ensure high-quality outputs in all supported formats.\\n* **Automatic Dynamic Drill-throughs for Vista Reports**\\n\\n Introducing a new way to explore data in Vista reports. With the latest update, users can now access", + "title": "March and April 2025 | Changelog | DevRev" }, { - "id": "ART-15687_KNOWLEDGE_NODE-1", - "text": "[Groups](/docs/product/groups)\\n + [Parts & trails](/docs/product/parts)\\n + [Vistas](/docs/product/vistas)\\n\\n - [Vista Reports](/docs/product/vista-reports)\\n - [Board view](/docs/product/board-view)\\n + [Tasks](/docs/product/tasks)\\n + [Updates](/docs/product/updates)\\n + [Customer email notifications](/docs/product/customer-emails)\\n + [Roles](/docs/product/roles)\\n\\n - [Default privileges by group](/docs/product/privs)\\n + [Access control](/docs/product/access-control)\\n +", + "id": "ART-15687_KNOWLEDGE_NODE-24", + "text": "\\xe2\\x86\\x97\\xef\\xb8\\x8f](/docs/DevRevU)\\n\\n + [Product demos](/docs/DevRevU/demos)\\n\\nOn this page\\n\\n* [Dashboards](#dashboards)\\n* [Creating widgets](#creating-widgets)\\n* [Creating dashboards](#creating-dashboards)\\n\\n1. [Documentation](/docs)\\n3. [Computer by DevRev](/docs/intro)\\n[Dashboards](/docs/dashboards/dashboard-creation)\\n\\nDashboards\\n----------\\n\\nDashboards in the DevRev app help users visualize and make sense of data spread across different objects. They are built using a", "title": "Dashboards | Computer by DevRev | DevRev" }, { - "id": "ART-1955_KNOWLEDGE_NODE-38", - "text": "allows a user to create a dashboard\\n\\n Privileges: dashboard object ['CREATE']\\n* *Dashboard Owner:* A role that allows the creator to view, edit and delete a dashboard\\n\\n Privileges: dashboard object ['READ', 'UPDATE', 'DELETE']\\n* *Question Answer Interactor:* Contains privileges on question answers for members of the default group 'Members'.\\n\\n Privileges: question\\\\_answer object ['CREATE', 'READ', 'UPDATE']\\n* *Dataset Creator:* A role that allows a user to create a dataset\\n\\n", - "title": "Default privileges by group | Roles | Computer by DevRev | DevRev" + "id": "ART-2666_KNOWLEDGE_NODE-30", + "text": "in Explore\\n\\nIn the **Explore** section, users can search for specific views using the search bar located in the top-left corner. Additionally, users can filter views by type, including:\\n\\n * **Dashboards**\\n * **Sprint Boards**\\n * **Vistas**\\n\\n### Pinning and unpinning views\\n\\nYou can now pin views from the **Explore** section directly to your left navigation menu or remove them for a more tailored experience. This feature ensures quick access to the most important views.\\n\\nTo pin or", + "title": "October 5: Left navigation | Changelog | DevRev" }, { - "id": "ART-15687_KNOWLEDGE_NODE-31", - "text": "dashboards\\n-------------------\\n\\nDashboards organize and display multiple widgets.\\n\\n* **Access the dashboard builder**:\\n Similar to the widget builder, access the dashboard builder by modifying your DevRev workspace URL. For example, your\\\\_workspace\\\\_slug/dashboard-preview.\\n The builder provides a boilerplate code.\\n\\n ![]()\\n* **Link widgets to the dashboard**:\\n\\n + Scroll to the section that defines the widgets to be linked.\\n + Remove any existing widget IDs and paste the", + "id": "ART-15687_KNOWLEDGE_NODE-0", + "text": "b'Dashboards | Computer by DevRev | DevRev\\n\\n* Computer\\n* Resources\\n* [Our Customers](/case-study)\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](/request-a-demo)\\n\\nComputer\\n\\nResources\\n\\n[Our Customers](/case-study)\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](/request-a-demo)\\n\\nSearch\\n\\n`CMD`\\xc2\\xa0+\\xc2\\xa0`K`\\n\\n* [Introduction](/docs)\\n* [Computer by DevRev](/docs/intro)\\n\\n + [Core concepts](/docs/product/core)\\n + [Apps](/docs/product/apps)\\n +", "title": "Dashboards | Computer by DevRev | DevRev" }, { - "id": "ART-15687_KNOWLEDGE_NODE-33", - "text": "organization.\\n Define the reference ID for each tab before mapping widgets to them.\\n* **Create the dashboard**:\\n Once satisfied with the linked widgets and layout, click the **Create dashboard** button.\\n* **Accessing dashboards**:\\n\\nSearch in the **Explore** section:\\n\\n* Go to **Explore** in the left nav in DevRev.\\n* Search for your dashboard by its name.\\n* Click on the dashboard to access it.\\n* For easy access, you can pin your dashboard under a section of your", - "title": "Dashboards | Computer by DevRev | DevRev" + "id": "ART-2662_KNOWLEDGE_NODE-1", + "text": "[Parts & trails](/docs/product/parts)\\n + [Vistas](/docs/product/vistas)\\n\\n - [Vista Reports](/docs/product/vista-reports)\\n - [Board view](/docs/product/board-view)\\n + [Tasks](/docs/product/tasks)\\n + [Updates](/docs/product/updates)\\n + [Customer email notifications](/docs/product/customer-emails)\\n + [Roles](/docs/product/roles)\\n\\n - [Default privileges by group](/docs/product/privs)\\n + [Access control](/docs/product/access-control)\\n + [Object", + "title": "DevRev Documentation" }, { - "id": "ART-15687_KNOWLEDGE_NODE-37", - "text": "Service](/legal/terms-of-service)\\n\\n[System Status](/status)\\n\\n\\xc2\\xa9 2025 DevRev Inc.\\n\\n![]()\\n\\n![]()\\n\\n![]()'", + "id": "ART-15687_KNOWLEDGE_NODE-34", + "text": "choice.\\n\\n[PreviousObject customization](/docs/product/object-customization)[NextGlossary \\xe2\\x86\\x97\\xef\\xb8\\x8f](/docshttps://support.devrev.ai/devrev/article/ART-16784-glossary)\\n\\n#### On this page\\n\\n* [Dashboards](#dashboards)\\n* [Creating widgets](#creating-widgets)\\n* [Creating dashboards](#creating-dashboards)\\n\\n[Enterprise grade security to protect customer data\\n\\nLearn more about it.\\n\\n![]()](/blog/soc-compliance)\\n\\nComputer\\n\\n* [Meet Computer](/meet-computer)\\n* [How Computer", "title": "Dashboards | Computer by DevRev | DevRev" } ] @@ -3868,39 +3868,44 @@ "query": "Escalation triggers for complex queries requiring human intervention, including probing questions and answer capturing", "retrievals": [ { - "id": "ART-1003_KNOWLEDGE_NODE-25", - "text": "* 100\\n \\n \\n\\n\\nSELECT (COUNT(*) * 100) / (SELECT COUNT(*) FROM tickets WHERE EXTRACT(@period FROM created_at) = EXTRACT(@period FROM CURRENT_DATE)) AS EscalationRate\\nFROM tickets\\nWHERE is_escalated = 1\\nAND EXTRACT(@period FROM created_at) = EXTRACT(@period FROM CURRENT_DATE);\\n-- NOTE: Replace @period with 'DAY', 'WEEK', 'MONTH', or 'QUARTER'.\\n\\n\\nAgent Utilization Rate\\n\\n\\n Definition\\n \\n The percentage of an engineer\\xe2\\x80\\x99s working hours spent on handling customer", - "title": "Understanding a Support Lead's Pain Points and KPIs" + "id": "ART-1709_KNOWLEDGE_NODE-12", + "text": "Significant cost overhead\\n\\n**After:**\\n\\n * AI-powered chatbot deflecting a huge portion of the basic incoming queries, in addition to email and live chat support\\n * Customer support scaled down to a team of two, handling complex queries that require human intervention.\\n * Cost-effective and optimized support operations, while maintaining customer satisfaction\\n\\n## Looking ahead\\n\\nPradeep believes the best customer service is when the customer does not have to reach out for support;", + "title": "ACC-qjz7ErXz - Mad Rewards: MadRewards uses DevRev\u2019s AI to modernize customer su" }, { - "id": "ART-1974_KNOWLEDGE_NODE-30", - "text": "stage.\\n* *Needs response* (NR)\\n\\n The customer has responded; the customer experience engineer needs to review the item and respond or resolve the issue if the user requests or validates the fix. When a customer experience engineer responds the stage transitions to *waiting on user*.\\n\\n In certain cases it may be necessary to escalate the item internally where the conversation may depend on tickets, issues, or a response from someone other than themselves. In this case the stage", - "title": "Conversations | Computer for Support Teams | DevRev" + "id": "ART-1771_KNOWLEDGE_NODE-7", + "text": "queries instantly, which frees up our human support agents to promptly address more complex issues.\\n\\n![]()\\n\\nAnkur ShresthaCo-Founder of Tough Trucks for Kids\\n\\nThe impact: Automation, scalability, measurable results\\n-------------------------------------------------------\\n\\n#### Powerful AI automation\\n\\nDevRev\\'s Conversational AI agent intelligently handles 85-90% of routine customer inquiries without human intervention, allowing the support team to focus on more complex issues that", + "title": "ToughTrucksForKids.com achieves dramatic efficiency gains and customer satisfaction through AI-powered support automation" }, { - "id": "ART-1983_KNOWLEDGE_NODE-28", - "text": "creation of Q&As, Computer learns from customer conversations\\xc2\\xa0in which a human answers a question that it previously could not answer.\\n\\nWhen a customer initiates a conversation seeking answers, Computer springs into action, drawing upon published Q&As and knowledge articles to provide a solution. If Computer falls short or the user prefers a more personalized touch, they opt to connect with a customer experience engineer and resolve the conversation. Computer doesn't just move", - "title": "Questions & answers | Computer for Support Teams | DevRev" + "id": "ART-4271_KNOWLEDGE_NODE-27", + "text": "via Workflows**\\n\\nSet up automated workflows to convert conversations to tickets based on specific triggers:\\n\\n * When a conversation is updated with certain criteria\\n * When your AI agent identifies an issue requiring escalation\\n * According to your custom business rules\\n\\nWorkflows enable seamless handovers from automated conversations to your support teams when necessary.\\n\\n## End user experience\\n\\n### PLuG widget experience\\n\\nWhen a conversation is converted to a ticket in the", + "title": "Convert Conversations to Tickets | Conversations | Support | DevRev" }, { - "id": "ART-1003_KNOWLEDGE_NODE-3", - "text": "transfer session (KT) with teams as new features go out?\\n\\nHow to resolve them:\\n\\n\\n Leverage intelligent deflection and AI offloads\\n \\n For example, don\\xe2\\x80\\x99t waste time making a human gather context, AI can now very accurately gather context and/or suggest articles.\\n \\n \\n Leverage load in terms of routing\\n \\n Normally routing is statically done or done in a round-robin manner, however, that doesn\\xe2\\x80\\x99t work when cases may be differing in complexity.\\n", - "title": "Understanding a Support Lead's Pain Points and KPIs" + "id": "ART-4172_KNOWLEDGE_NODE-3", + "text": "enlist a balance between AI, Automation and Human approaches to meet these goals. Our AI Support Agent is designed to enhance the efficiency of customer service operations by interacting with users to resolve common queries to taking complex actions. The majority of the time (>50%), our AI Support Agent can address our customers\\xe2\\x80\\x99 needs; however, in the event an issue is not resolved, the agent seamlessly escalates the conversation by creating a ticket. This hybrid approach of", + "title": "DevRev Service Level Agreement" }, { - "id": "ART-1004_KNOWLEDGE_NODE-4", - "text": "these resources most productive, it is important to leverage automation to handle some of these lower-level activities; then, by the time it reaches the engineer, they are dealing with more complex pieces of the puzzle. Examples of this are KB deflection, Q&A flows (gather context), and system offloads (AI is great here).\\n\\nA great example is the monotony and frequency of \\xe2\\x80\\x9cWhat\\xe2\\x80\\x99s the status of this?\\xe2\\x80\\x9d inquiries. If people have access to the system, and the", - "title": "Understanding a Support Engineer's Pain Points and KPIs" + "id": "ART-13178_KNOWLEDGE_NODE-7", + "text": "up with customers at appropriate intervals, and escalate issues only when resolution criteria aren\\xe2\\x80\\x99t met.\\n * **Tool-proficient:** Leverages various digital tools and systems to accomplish tasks. For instance, AI agents can access inventory databases, shipping systems, and customer records to resolve queries about complex order fulfillments.\\n * **Continuously learning:** Improves performance through feedback loops and experience accumulation. For example, an agentic artificial", + "title": "Understanding Agentic AI: Capabilities and Implications for the Future" }, { - "id": "ART-1974_KNOWLEDGE_NODE-28", - "text": "transitions from *new* to *waiting on user*. When a customer responds back to support, the stage transitions to *needs response*.\\n\\n Towards the end of the conversation when the resolution is expected to be valid, the customer experience engineer asks the customer to acknowledge their concerns have been resolved. When the customer experience engineer asks this question the stage transitions to *waiting on user*, and if they validate it moves to *needs response* for the customer experience", - "title": "Conversations | Computer for Support Teams | DevRev" + "id": "ART-1036_KNOWLEDGE_NODE-10", + "text": "be tackled decisively instead of escalating\\n\\n![]()\\n\\nDhruv AgrawalCOO & Co-founder, Shipsy\\n\\n### 5. Less time managing work, more time building product\\n\\nShipsy leveraged Computer\\xe2\\x80\\x99s Foundational Services to set up automations like:\\n\\n* Notifications for aging tickets\\n* Time-based triggers to prevent SLA breaches\\n* Approval funnels for product managers to prioritize projects\\n\\nImpact and results\\n------------------\\n\\nShipsy's implementation of DevRev Support and", + "title": "Shipsy elevates logistics support with AI-powered automation and cross team collaboration" }, { - "id": "ART-1983_KNOWLEDGE_NODE-27", - "text": "**Q&As** and click **+ QA** in the top-right corner.\\n2. Fill in the **Question** and **Answer** fields, and select the relevant **Part**.\\n3. Set the appropriate **Status** and **Access level**. Set the status to *External* or *Public* if you want Computer to use it.\\n4. Confirm by clicking **Create**.\\n\\n![]()\\n\\nAutomatic creation\\n------------------\\n\\nYour customer conversations include a lot of knowledge, including some of the most accurate and current information. With the automated", - "title": "Questions & answers | Computer for Support Teams | DevRev" + "id": "ART-13178_KNOWLEDGE_NODE-4", + "text": "traditional AI that simply responds to specific queries, agentic AI can make decisions, execute multiple steps, and complete tasks with minimal human intervention, allowing for greater operational efficiency.\\n\\nThink of agentic AI as a digital assistant that doesn\\xe2\\x80\\x99t just answer your questions but actively works to achieve outcomes for you. These autonomous agents can plan sequences of actions, use various tools and systems, adapt to new information, and persist until completing the", + "title": "Understanding Agentic AI: Capabilities and Implications for the Future" + }, + { + "id": "ART-15716_KNOWLEDGE_NODE-9", + "text": "tickets for escalation or tracking.\\n\\nQuick summary: If you\\xe2\\x80\\x99re a customer, you create tickets. If you\\xe2\\x80\\x99re a developer, you create issues.PLuG widget and SDK\\n\\nIntegrating PluG in React Native Expo Apps\\n\\nPluG is designed for web, but you can embed it in a React Native Expo app using react-native-webview. Install the package with npx expo install react-native-webview, then use a WebView component to load your PluG widget\\xe2\\x80\\x99s URL. Some advanced features may not", + "title": "Support queries related playbook" }, { "id": "ART-1987_KNOWLEDGE_NODE-27", @@ -3908,14 +3913,9 @@ "title": "Turing AI agent | Computer for Support Teams | DevRev" }, { - "id": "ART-1004_KNOWLEDGE_NODE-2", - "text": "troubleshooting.\\n\\nKPIs to track:\\n\\n\\n First Contact Resolution Rate\\n Knowledge Base Contributions\\n\\n\\nHigh-pressure environment\\n\\nDealing with people are angry or frustrated isn\\xe2\\x80\\x99t easy, even for the calmest person. In their role, they are the primary person triaging requets from customers and status updates from others in the organization; this can make this a very complex and tense role.\\n\\nAdditionally, most support organizations are very speed focused, so there is pressure", - "title": "Understanding a Support Engineer's Pain Points and KPIs" - }, - { - "id": "ART-1003_KNOWLEDGE_NODE-13", - "text": "this is ensuring you have visibility helping foster communication between internal teams. If you see an increase in escalations, that could point to a lack of enablement for the team.\\n\\nKPIs to track:\\n\\n\\n Escalation Rate\\n Time to Escalation Resolution\\n\\n\\nStaff retention and development\\n\\nAs much as you must support your customers, it\\xe2\\x80\\x99s also imperative to attract, retain, and develop top talent. How can you help enable them? Are you helping them grow? If the staff gets burnt", - "title": "Understanding a Support Lead's Pain Points and KPIs" + "id": "ART-970_KNOWLEDGE_NODE-48", + "text": "of escalations and have that status automatically reflected in the ticket?\\n\\n\\nSales Representative:\\n\\n\\n What if you had full visibility and could easily monitor the challenges your customers face, receiving notifications when issues arise?\\n What if you could prioritize certain fixes based on deal size?\\n Imagine having immediate insight into matters that your customers care about or being promptly notified about new developments from the engineering team.\\n\\n\\nCustomer Success:\\n\\n\\n", + "title": "The Story" } ] }, @@ -3924,54 +3924,54 @@ "query": "API token vs Auth token for API calling DevRev", "retrievals": [ { - "id": "ART-1386_KNOWLEDGE_NODE-8", - "text": "[Documentation](https://docs.devrev.ai/)\\n * [API Reference](https://docs.devrev.ai/api/)\\n * [The Book of DevRev](https://thebook.devrev.ai/)\\n * [Partner Program](https://devrev.ai/partners)\\n * [Startup Program](https://devrev.ai/startups)\\n\\nCompany\\n\\n * [About](https://devrev.ai/about)\\n * [People](https://devrev.ai/people)\\n * [Careers](https://devrev.ai/careers)\\n * [Places](https://devrev.ai/places)\\n * [Invest](https://revd.devrev.ai/)\\n * [What Why", - "title": "Get Auth Token \u2014 DevRev | Docs" + "id": "ART-1472_KNOWLEDGE_NODE-17", + "text": "auth: githubPAT, \\n 4| });\\n[/code] \\n \\nTo facilitate authentication for DevRev API calls, a DevRev token is required. The initialization process for the DevRev SDK involves using the received endpoint.\\n\\n[code]\\n\\n 1| const devrevToken = event.context.secrets.service_account_token; \\n ---|--- \\n 2| const endpoint = event.execution_metadata.devrev_endpoint; \\n 3| const devrevSDK = client.setup({ \\n 4| endpoint: endpoint, \\n 5| token: devrevToken, \\n 6|", + "title": "Using a snap-in to perform an external action \u2014 DevRev | Docs" }, { - "id": "ART-1384_KNOWLEDGE_NODE-9", - "text": "Engine](https://devrev.ai/workflow-engine)\\n * [Turing AI](https://devrev.ai/turing-ai)\\n\\nResources\\n\\n * [Pricing](https://devrev.ai/pricing/support)\\n * [Blog](https://devrev.ai/blog)\\n * [Events](https://devrev.ai/events)\\n * [News](https://devrev.ai/blog?category=news)\\n * [Case Studies](https://devrev.ai/case-study)\\n * [Documentation](https://docs.devrev.ai/)\\n * [API Reference](https://docs.devrev.ai/api/)\\n * [The Book of DevRev](https://thebook.devrev.ai/)\\n * [Partner", - "title": "Create Auth Token \u2014 DevRev | Docs" + "id": "ART-1193_KNOWLEDGE_NODE-0", + "text": "b'Security tokens | DevRev | Docs\\n\\n[![]()![]()](https://developer.devrev.ai/)\\n\\nPublic\\n\\nPublic\\n\\nSearch\\n\\n`/`\\n\\n[API Reference](/api-reference/getting-started)[auth-tokens](/api-reference/auth-tokens/security-tokens)\\n\\nSecurity tokens\\n===============\\n\\nCopy page\\n\\n`auth-tokens` endpoint\\n\\n\\xe2\\x84\\xb9\\xef\\xb8\\x8f Security tokens are required for accessing DevRev. There are four types of security tokens:\\n\\n* **Application Access Token (AAT)**: Uniquely identifies an application", + "title": "Security tokens | DevRev | Docs" }, { - "id": "ART-1388_KNOWLEDGE_NODE-9", - "text": "[Documentation](https://docs.devrev.ai/)\\n * [API Reference](https://docs.devrev.ai/api/)\\n * [The Book of DevRev](https://thebook.devrev.ai/)\\n * [Partner Program](https://devrev.ai/partners)\\n * [Startup Program](https://devrev.ai/startups)\\n\\nCompany\\n\\n * [About](https://devrev.ai/about)\\n * [People](https://devrev.ai/people)\\n * [Careers](https://devrev.ai/careers)\\n * [Places](https://devrev.ai/places)\\n * [Invest](https://revd.devrev.ai/)\\n * [What Why", - "title": "List Auth Tokens \u2014 DevRev | Docs" + "id": "ART-1276_KNOWLEDGE_NODE-13", + "text": "|\\n```\\n\\nTo facilitate authentication for DevRev API calls, a DevRev token is required.\\nThe initialization process for the DevRev SDK involves using the received endpoint.\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | const devrevToken = event.context.secrets.service_account_token; |\\n| 2 | const endpoint = event.execution_metadata.devrev_endpoint; |\\n| 3 | const devrevSDK = client.setup({ |\\n| 4 | endpoint: endpoint, |\\n| 5 | token: devrevToken, |\\n| 6 | }); |\\n```\\n\\nWith the SDKs successfully", + "title": "Using a snap-in to perform an external action | DevRev | Docs" }, { - "id": "ART-1386_KNOWLEDGE_NODE-11", - "text": "AI?](https://devrev.ai/what-is-conversational-ai)\\n\\n[](https://devrev.ai)\\n\\n[](https://www.linkedin.com/company/devrev)[](https://medium.com/devrev)[](https://twitter.com/devrev)\\n\\n[System Status](https://devrev.ai/status)\\n\\n\\xc2\\xa9 2025 DevRev Inc.\\n\\n[](https://devrev.ai)\\n\\n * Product\\n * Platform\\n * Solutions\\n * Marketplace\\n * Company\\n * Resources\\n * [Pricing](https://devrev.ai/pricing)\\n\\n __\\n\\n[Login](https://app.devrev.ai/login)[Book a", - "title": "Get Auth Token \u2014 DevRev | Docs" + "id": "ART-1362_KNOWLEDGE_NODE-5", + "text": "APIs on behalf of the corresponding dev user. The lifetime of a PAT is usually in days. The subject of the PAT is set to the corresponding dev users DON (for example, `don:identity:dvrv-us-1:devo/0:devu/30`).\\n\\n## Personal access token usage\\n\\nAuthentication to DevRev APIs requires a personal access token (PAT). A PAT is used to uniquely identify a dev user in context of a dev org and can be used by external third-party applications to access DevRev APIs on behalf of the corresponding dev", + "title": "Authentication \u2014 DevRev | Docs" }, { - "id": "ART-1196_KNOWLEDGE_NODE-6", - "text": "with](https://buildwithfern.com/?utm_campaign=buildWith&utm_medium=docs&utm_source=developer.devrev.ai)'", - "title": "Get Auth Token | DevRev | Docs" + "id": "ART-1170_KNOWLEDGE_NODE-5", + "text": "DevRev APIs on behalf of the corresponding dev user. The lifetime of a PAT is usually in days. The subject of the PAT is set to the corresponding dev users DON (for example, `don:identity:dvrv-us-1:devo/0:devu/30`).\\n\\nPersonal access token usage\\n---------------------------\\n\\nAuthentication to DevRev APIs requires a personal access token (PAT). A PAT is used to uniquely identify a dev user in context of a dev org and can be used by external third-party applications to access DevRev APIs on", + "title": "Authentication | DevRev | Docs" }, { - "id": "ART-1394_KNOWLEDGE_NODE-9", - "text": "* [Blog](https://devrev.ai/blog)\\n * [Events](https://devrev.ai/events)\\n * [News](https://devrev.ai/blog?category=news)\\n * [Case Studies](https://devrev.ai/case-study)\\n * [Documentation](https://docs.devrev.ai/)\\n * [API Reference](https://docs.devrev.ai/api/)\\n * [The Book of DevRev](https://thebook.devrev.ai/)\\n * [Partner Program](https://devrev.ai/partners)\\n * [Startup Program](https://devrev.ai/startups)\\n\\nCompany\\n\\n * [About](https://devrev.ai/about)\\n *", - "title": "Get Auth Token (POST) \u2014 DevRev | Docs" + "id": "ART-16579_KNOWLEDGE_NODE-12", + "text": "replace the `` and `` with the actual values.\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl \\\\ |\\n| > | --location \\'https://api.devrev.ai/auth-tokens.create\\' \\\\ |\\n| > | --header \\'accept: application/json, text/plain, */*\\' \\\\ |\\n| > | --header \\'content-type: application/json\\' \\\\ |\\n| > | --header \\'authorization: \\' \\\\ |\\n| > | --data \\'{ |\\n| > | \"rev_info\": { |\\n| > | \"user_ref\": \"\" |\\n| > | } |\\n| > | }\\' |\\n```\\n\\nThe response of the API call", + "title": "Features | DevRev | Docs" }, { - "id": "ART-1384_KNOWLEDGE_NODE-4", - "text": "that identifies the token.\\n\\n### Response\\n\\nResponse for the request to create a new token corresponding to the requested token type.\\n\\naccess_tokenstring`format: \"text\"`\\n\\nThe issued JSON Web Token (JWT) corresponding to the requested token type.\\n\\nexpires_inlong\\n\\nThe validity lifetime of the token specified in seconds since Unix epoch.\\n\\ntoken_typeenum\\n\\nAllowed values: bearer\\n\\nThe type of the issued token. Bearer is the only supported token type.\\n\\nclient_idstringOptional`format:", - "title": "Create Auth Token \u2014 DevRev | Docs" + "id": "ART-15506_KNOWLEDGE_NODE-5", + "text": "token\\n------------------------\\n\\n##### \\n\\nFor security reasons, this API call must be made from the server side to prevent exposing your application access token (AAT).\\n\\nUsing the `rev_info` method, you can generate and recognize a user within the DevRev system by providing relevant user details. This method enables you to convey information systematically, ensuring alignment between your DevRev CRM and the structured data model. For information regarding terminologies, click", + "title": "Identify your users with Plug | DevRev | Docs" }, { - "id": "ART-12969_KNOWLEDGE_NODE-6", - "text": "DevRev](https://thebook.devrev.ai/)\\n * [Partner Program](https://devrev.ai/partners)\\n * [Startup Program](https://devrev.ai/startups)\\n\\nCompany\\n\\n * [About](https://devrev.ai/about)\\n * [People](https://devrev.ai/people)\\n * [Careers](https://devrev.ai/careers)\\n * [Places](https://devrev.ai/places)\\n * [Invest](https://revd.devrev.ai/)\\n * [What Why How](https://devrev.ai/what-why-how)\\n\\nConnect\\n\\n * [Contact ](mailto:humansofdevrev@devrev.ai)\\n * [Instagram", - "title": "Info Auth Tokens \u2014 DevRev | Docs" + "id": "ART-12970_KNOWLEDGE_NODE-1", + "text": "__\\n\\n[Pricing](https://devrev.ai/pricing)\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](https://devrev.ai/request-a-demo)\\n\\n[API Reference](/public/api-reference/getting-started)[Auth Tokens](/public/api-reference/auth-tokens/create)\\n\\n# Info Auth Tokens (POST)\\n\\nPOST\\n\\nhttps://api.devrev.ai/auth-tokens.info\\n\\nTry it\\n\\nReturns the Dev organization, user and token attributes extracted from the auth token.\\n\\n### Request\\n\\nThis endpoint expects an object.\\n\\n### Response\\n\\nThe Dev", + "title": "Info Auth Tokens (POST) \u2014 DevRev | Docs" }, { - "id": "ART-1384_KNOWLEDGE_NODE-13", - "text": "AI?](https://devrev.ai/what-is-conversational-ai)\\n\\n[](https://devrev.ai)\\n\\n[](https://www.linkedin.com/company/devrev)[](https://medium.com/devrev)[](https://twitter.com/devrev)\\n\\n[System Status](https://devrev.ai/status)\\n\\n\\xc2\\xa9 2025 DevRev Inc.\\n\\n[](https://devrev.ai)\\n\\n * Product\\n * Platform\\n * Solutions\\n * Marketplace\\n * Company\\n * Resources\\n * [Pricing](https://devrev.ai/pricing)\\n\\n __\\n\\n[Login](https://app.devrev.ai/login)[Book a", - "title": "Create Auth Token \u2014 DevRev | Docs" + "id": "ART-1789_KNOWLEDGE_NODE-62", + "text": "2023-01-01T12:00:00Z \" , 11 \" requested_token_type \" : \" urn:devrev:params:oauth:token-type:aat \" , 12 \" scopes \" : [ 13 \" scopes \" 14 ] , 15 \" status \" : \" active \" , 16 \" subject \" : \" subject \" , 17 \" token_hint \" : \" token_hint \" 18 } 19 ] 20 }\\nAPI Reference auth-tokens List Post.\\n\\nPOST https:// api.devrev.ai / auth-tokens.list\\nGets the token metadata for all the tokens corresponding to the given token type issued for a given subject.\\nRequest.\\n\\nThis endpoint expects an", + "title": "List \u2014 DevRev | Docs" }, { - "id": "ART-1384_KNOWLEDGE_NODE-8", - "text": "it.](https://devrev.ai/blog/soc-compliance)\\n\\nProduct\\n\\n * [Build](https://devrev.ai/build)\\n * [Support](https://devrev.ai/support)\\n * [Search](https://devrev.ai/search)\\n * [PLuG - User Engagement](https://devrev.ai/plug-user-engagement)\\n * [PLuG - User Observability](https://devrev.ai/plug-observability)\\n * [Marketplace](https://marketplace.devrev.ai/)\\n\\nPlatform\\n\\n * [Airdrop](https://devrev.ai/airdrop)\\n * [Analytics](https://devrev.ai/analytics)\\n * [Workflow", - "title": "Create Auth Token \u2014 DevRev | Docs" + "id": "ART-1198_KNOWLEDGE_NODE-0", + "text": "b'List Auth Tokens | DevRev | Docs\\n\\n[![]()![]()](https://developer.devrev.ai/)\\n\\nPublic\\n\\nPublic\\n\\nSearch\\n\\n`/`\\n\\n[API Reference](/api-reference/getting-started)[auth-tokens](/api-reference/auth-tokens/security-tokens)\\n\\nList Auth Tokens\\n================\\n\\nCopy page\\n\\nGET\\n\\nhttps://api.devrev.ai/auth-tokens.list\\n\\nGET\\n\\n/auth-tokens.list\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl https://api.devrev.ai/auth-tokens.list \\\\ |\\n| > | -H \"Authorization: Bearer \" |\\n```\\n\\n[Try", + "title": "List Auth Tokens | DevRev | Docs" } ] }, @@ -3985,49 +3985,49 @@ "title": "Service-level agreement | Computer for Support Teams | DevRev" }, { - "id": "ART-1972_KNOWLEDGE_NODE-24", - "text": "[Product demos](/docs/DevRevU/demos)\\n\\n1. [Documentation](/docs)\\n3. [Computer for Support Teams](/docs/product/support)\\n[Support analytics](/docs/product/support-analytics)\\n[Ticket-SLA Analytics](/docs/dashboards/ticket-sla-analytics)\\n\\nTicket-SLA Analytics\\n====================\\n\\n* **SLA applied Tickets**\\n\\n Number of tickets where SLA is applied.\\n* **SLA compliance rate**\\n\\n Percentage of tickets where SLA was met out of all tickets where SLA is applied.\\n* **Active tickets with", - "title": "Ticket-SLA Analytics | Support analytics | Computer for Support Teams | DevRev" + "id": "ART-1831_KNOWLEDGE_NODE-476", + "text": "Optional\\nFilters for tickets with any of the provided severities.\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\nFilters for records with any of the provided SLA stages.\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\nFilters for tickets with any of the provided source channels.\\nticket.subtype string Optional\\nFilters for tickets with any of the provided subtypes.\\ntype enum Optional\\nFilters for work of the", + "title": "Get \u2014 DevRev | Docs" }, { - "id": "ART-1972_KNOWLEDGE_NODE-15", - "text": "[Operational SLA Metrics](/docs/automations/operational-sla-metrics)\\n - [Custom field migration](/docs/automations/custom-field-migration)\\n - [Slack scraper](/docs/automations/slack-scraper)\\n - [Slack Broadcaster](/docs/automations/slack-broadcaster)\\n - [Reported by enricher](/docs/automations/ticket-reported-by)\\n - [Ticket approval workflow](/docs/automations/ticket-approval-workflow)\\n - [Ticket linked issues comment", - "title": "Ticket-SLA Analytics | Support analytics | Computer for Support Teams | DevRev" + "id": "ART-1829_KNOWLEDGE_NODE-476", + "text": "Optional\\nFilters for tickets with any of the provided severities.\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\nFilters for records with any of the provided SLA stages.\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\nFilters for tickets with any of the provided source channels.\\nticket.subtype string Optional\\nFilters for tickets with any of the provided subtypes.\\ntype enum Optional\\nFilters for work of the", + "title": "Delete \u2014 DevRev | Docs" }, { - "id": "ART-1972_KNOWLEDGE_NODE-4", - "text": "analytics](/docs/product/support-analytics)\\n\\n - [Conversation insights](/docs/dashboards/conversation-insights)\\n - [Conversation-SLA Analytics](/docs/dashboards/conversation-sla-analytics)\\n - [Conversation-Team Performance](/docs/dashboards/conversation-team-performance)\\n - [Ticket insights](/docs/dashboards/ticket-insights)\\n - [Ticket-SLA Analytics](/docs/dashboards/ticket-sla-analytics)\\n - [Ticket-Team Performance](/docs/dashboards/ticket-team-performance)\\n +", - "title": "Ticket-SLA Analytics | Support analytics | Computer for Support Teams | DevRev" + "id": "ART-1588_KNOWLEDGE_NODE-465", + "text": "Optional\\nFilters for tickets with any of the provided severities.\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\nFilters for records with any of the provided SLA stages.\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\nFilters for tickets with any of the provided source channels.\\nticket.subtype string Optional\\nFilters for tickets with any of the provided subtypes.\\ntype enum Optional\\nFilters for work of the", + "title": "Get \u2014 DevRev | Docs" }, { - "id": "ART-1972_KNOWLEDGE_NODE-25", - "text": "SLA breaches**\\n\\n Number of Active Tickets that breached an SLA.\\n* **Tickets with SLA warning**\\n\\n Number of Active Tickets that about to breach an SLA.\\n* **Resolution compliance rate**\\n\\n Percentage of tickets where Resolution SLA was met out of all tickets where Resolution SLA is applied.\\n* **First Response compliance rate**\\n\\n Percentage of tickets where First Response SLA was met out of all tickets where First Response SLA is applied.\\n* **Next Response compliance rate**\\n\\n", - "title": "Ticket-SLA Analytics | Support analytics | Computer for Support Teams | DevRev" + "id": "ART-1830_KNOWLEDGE_NODE-476", + "text": "Optional\\nFilters for tickets with any of the provided severities.\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\nFilters for records with any of the provided SLA stages.\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\nFilters for tickets with any of the provided source channels.\\nticket.subtype string Optional\\nFilters for tickets with any of the provided subtypes.\\ntype enum Optional\\nFilters for work of the", + "title": "Get Post \u2014 DevRev | Docs" }, { - "id": "ART-1986_KNOWLEDGE_NODE-45", - "text": "selected on the ticket is not assigned any SLA.\\n\\n\\xc2\\xa0\\xc2\\xa0 \\xc2\\xa0 - Action: Check your SLA assignment rules or add the customer as an exception to any of your SLAs.\\n\\n![]()\\n\\nThe **SLA Name** is never empty if your organization has a default SLA.\\n\\n1. Verify policy conditions:\\n\\n\\xc2\\xa0\\xc2\\xa0 - If the **SLA Name** is populated but you still see no SLA metrics running on the ticket, the ticket does not satisfy the conditions of any policy within the SLA.\\n\\n\\xc2\\xa0\\xc2\\xa0", - "title": "Service-level agreement | Computer for Support Teams | DevRev" + "id": "ART-1824_KNOWLEDGE_NODE-460", + "text": "Optional\\nFilters for tickets with any of the provided severities.\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\nFilters for records with any of the provided SLA stages.\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\nFilters for tickets with any of the provided source channels.\\nticket.subtype string Optional\\nFilters for tickets with any of the provided subtypes.\\ntype enum Optional\\nFilters for work of the", + "title": "Delete \u2014 DevRev | Docs" }, { - "id": "ART-2017_KNOWLEDGE_NODE-4", - "text": "analytics](/docs/product/support-analytics)\\n\\n - [Conversation insights](/docs/dashboards/conversation-insights)\\n - [Conversation-SLA Analytics](/docs/dashboards/conversation-sla-analytics)\\n - [Conversation-Team Performance](/docs/dashboards/conversation-team-performance)\\n - [Ticket insights](/docs/dashboards/ticket-insights)\\n - [Ticket-SLA Analytics](/docs/dashboards/ticket-sla-analytics)\\n - [Ticket-Team Performance](/docs/dashboards/ticket-team-performance)\\n +", - "title": "SLA status change Slack notifier | Automate | Snap-ins | DevRev" + "id": "ART-1823_KNOWLEDGE_NODE-461", + "text": "Optional\\nFilters for tickets with any of the provided severities.\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\nFilters for records with any of the provided SLA stages.\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\nFilters for tickets with any of the provided source channels.\\nticket.subtype string Optional\\nFilters for tickets with any of the provided subtypes.\\ntype enum Optional\\nFilters for work of the", + "title": "Get \u2014 DevRev | Docs" }, { - "id": "ART-1986_KNOWLEDGE_NODE-42", - "text": "Target\\n------------------------------------\\n\\nIn order to filter tickets based on SLA, you can use the **Next SLA Target** filter.\\nHere\\xe2\\x80\\x99s how the filter works:\\n\\n* **All**: Filters all tickets that currently have an SLA applied to them. It will not filter tickets that had an SLA applied in the past and have been completed.\\n* **Breached since**:\\n\\n + **Any**: Filters all tickets that breached SLA, irrespective of when they were breached.\\n + **Over an hour**: Filters all", - "title": "Service-level agreement | Computer for Support Teams | DevRev" + "id": "ART-1651_KNOWLEDGE_NODE-468", + "text": "Optional\\nFilters for tickets with any of the provided severities.\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\nFilters for records with any of the provided SLA stages.\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\nFilters for tickets with any of the provided source channels.\\nticket.subtype string Optional\\nFilters for tickets with any of the provided subtypes.\\ntype enum Optional\\nFilters for work of the", + "title": "Create \u2014 DevRev | Docs" }, { - "id": "ART-1972_KNOWLEDGE_NODE-27", - "text": "by Channel**\\n\\n Number of tickets where SLA was breached for each source channel.\\n* **SLA breaches by Subtype**\\n\\n Number of tickets where SLA was breached for each ticket subtype.\\n* **SLA breaches by Owner**\\n\\n Number of Tickets with SLA breaches for ticket owners.\\n* **Avg CSAT by SLA status**\\n\\n Average CSAT rating of tickets w.r.t. their SLA status and severity.\\n* **Unassigned Tickets with SLA breaches per Customer**\\n\\n Number of Unassigned Tickets with SLA breaches for each", - "title": "Ticket-SLA Analytics | Support analytics | Computer for Support Teams | DevRev" + "id": "ART-1607_KNOWLEDGE_NODE-465", + "text": "Optional\\nFilters for tickets with any of the provided severities.\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\nFilters for records with any of the provided SLA stages.\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\nFilters for tickets with any of the provided source channels.\\nticket.subtype string Optional\\nFilters for tickets with any of the provided subtypes.\\ntype enum Optional\\nFilters for work of the", + "title": "Get Post \u2014 DevRev | Docs" }, { - "id": "ART-2818_KNOWLEDGE_NODE-4", - "text": "insights](/docs/dashboards/conversation-insights)\\n - [Conversation-SLA Analytics](/docs/dashboards/conversation-sla-analytics)\\n - [Conversation-Team Performance](/docs/dashboards/conversation-team-performance)\\n - [Ticket insights](/docs/dashboards/ticket-insights)\\n - [Ticket-SLA Analytics](/docs/dashboards/ticket-sla-analytics)\\n - [Ticket-Team Performance](/docs/dashboards/ticket-team-performance)\\n + [Conversations](/docs/product/conversation)\\n\\n - [Conversation to", - "title": "Operational SLA Metrics | Automate | Snap-ins | DevRev" + "id": "ART-1633_KNOWLEDGE_NODE-467", + "text": "Optional\\nFilters for tickets with any of the provided severities.\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\nFilters for records with any of the provided SLA stages.\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\nFilters for tickets with any of the provided source channels.\\nticket.subtype string Optional\\nFilters for tickets with any of the provided subtypes.\\ntype enum Optional\\nFilters for work of the", + "title": "List \u2014 DevRev | Docs" } ] }, @@ -4036,54 +4036,54 @@ "query": "automatically change ticket stage when customer responds", "retrievals": [ { - "id": "ART-1979_KNOWLEDGE_NODE-43", - "text": "*awaiting customer response* until the customer responds.\\n\\n In certain scenarios, the customer experience engineer may be able to resolve the customer's concern. If that's the case, they would ask the customer if their resolution has resolved their concern and the stage would move to the *awaiting customer response*. Once the concern is resolved and the customer acknowledges the resolution, the stage may move to *resolved*. If the concern isn't resolved, the stage may change back to *work in", + "id": "ART-1979_KNOWLEDGE_NODE-45", + "text": "a user. In certain cases where the ticket depends on some fix (issues) the stage may go from *in development* to *awaiting customer response* when the corresponding issues have been resolved and the fix needs to be validated with the user.\\n\\n In certain cases, the customer experience engineer may be able to solve directly (without any required issues) which may change the stage from *work in progress* to *awaiting customer response* to validate they have solved the problem. If either has", "title": "Tickets | Computer for Support Teams | DevRev" }, { - "id": "ART-1981_KNOWLEDGE_NODE-28", - "text": "new conversation. Respond within 1 hour to new messages on existing conversations. Change the stage of conversation to *awaiting customer response* as soon as you have responded.\\n* In **Updates**, filter by **Type** > **Mentioned**. Respond to those updates first.\\n* Create a ticket if you aren't able to resolve the conversation in 20 minutes. As soon as the ticket is opened, move it to the *escalate* stage. The owner of the ticket is the owner of the customer org where the conversation", - "title": "Support best practices | Computer for Support Teams | DevRev" + "id": "ART-1974_KNOWLEDGE_NODE-30", + "text": "stage.\\n* *Needs response* (NR)\\n\\n The customer has responded; the customer experience engineer needs to review the item and respond or resolve the issue if the user requests or validates the fix. When a customer experience engineer responds the stage transitions to *waiting on user*.\\n\\n In certain cases it may be necessary to escalate the item internally where the conversation may depend on tickets, issues, or a response from someone other than themselves. In this case the stage", + "title": "Conversations | Computer for Support Teams | DevRev" }, { - "id": "ART-1953_KNOWLEDGE_NODE-31", - "text": "stage of a ticket/conversation\\n----------------------------------------\\n\\n* **Trigger**: When there\\'s a change of stage in a ticket or conversation.\\n* **Action**: The system sends out a notification detailing the Ticket/Conversation number and stage change.\\n* **Sender**: {Company\\\\_Name} [support@yourdomain.com](mailto:support@yourdomain.com)\\n* **Subject**:\\n + For ticket: \"[{Company\\\\_Name}] Update on TKT-XXX - Ticket Title\"\"\"\\n + For conversations:", + "id": "ART-1953_KNOWLEDGE_NODE-24", + "text": "conversation](#reply-to-the-customer-on-a-conversation)\\n* [Reply to the customer on a ticket](#reply-to-the-customer-on-a-ticket)\\n* [Ticket linked to a conversation](#ticket-linked-to-a-conversation)\\n* [Change of stage of a ticket/conversation](#change-of-stage-of-a-ticketconversation)\\n* [CSAT survey for conversation/ticket](#csat-survey-for-conversationticket)\\n* [Auto customer reply](#auto-customer-reply)\\n* [Auto reply on email](#auto-reply-on-email)\\n\\n1. [Documentation](/docs)\\n3.", "title": "Customer email notifications | Computer by DevRev | DevRev" }, { - "id": "ART-2009_KNOWLEDGE_NODE-28", - "text": "ticket's stage when linked issue is linked or unlinked.\\n* Close pending tickets if they have remained in the *Awaiting customer response* stage for longer than x days.\\n* Update ticket's stage to waiting on user when user reverts on new conversation.\\n* Update ticket's stage to *Accepted* and notify owner and customers when an enhancement in ideation stage is linked.\\n* Update a spam conversation's stage to *Suspended*.\\n* Update a spam ticket's stage to", - "title": "Convergence | Automate | Snap-ins | DevRev" + "id": "ART-2012_KNOWLEDGE_NODE-28", + "text": "say \\xe2\\x80\\x9cI would like to add a terminal stage on my tickets\\xe2\\x80\\x9d and we will get it done.\\n\\n * If no terminal stage is set, tickets will reopen on new comments from customers if **Reopen Closed Tickets on customer message** is enabled in the [convergence snap-in](./converge). The tickets move to the _In Progress_ state by default.\\n\\n * If you connected your support email address with DevRev, it is recommended that you enable the **Allow automations to send email** in your", + "title": "Follow-up ticket | Automate | Snap-ins | DevRev" }, { - "id": "ART-1981_KNOWLEDGE_NODE-27", - "text": "Periodically group the **Inbox** by stage and make sure there conversations only in *hold* or *awaiting customer response* stages.\\n* Let the customer know when a ticket linked to a conversation is closed and request their verification.\\n* Once all tickets of a conversation are resolved and the customer is satisfied, resolve the conversation.\\n* Move new tickets to the *awaiting product assist* stage.\\n\\nRespond to conversations\\n------------------------\\n\\n* Respond as fast as possible to any", - "title": "Support best practices | Computer for Support Teams | DevRev" + "id": "ART-1979_KNOWLEDGE_NODE-47", + "text": "validate the fix with the user and then to *resolved*. If the user wants to cancel the ticket then the stage moves to *canceled*.\\n\\n**Closed**\\n\\n* *Canceled* (C)\\n\\n The ticket is determined to be invalid either by the user or the customer experience engineer. In certain scenarios, a ticket may have been created by accident and may be canceled by the creator. In other scenarios, garbage tickets may be created through automation or because of spam. Automation or the customer experience", + "title": "Tickets | Computer for Support Teams | DevRev" }, { - "id": "ART-1974_KNOWLEDGE_NODE-30", - "text": "stage.\\n* *Needs response* (NR)\\n\\n The customer has responded; the customer experience engineer needs to review the item and respond or resolve the issue if the user requests or validates the fix. When a customer experience engineer responds the stage transitions to *waiting on user*.\\n\\n In certain cases it may be necessary to escalate the item internally where the conversation may depend on tickets, issues, or a response from someone other than themselves. In this case the stage", - "title": "Conversations | Computer for Support Teams | DevRev" + "id": "ART-4271_KNOWLEDGE_NODE-25", + "text": "is being replaced with a new **Convert to Ticket** feature. This change provides a more seamless transition from conversation to ticket management.\\n\\n## How Conversation conversion works\\n\\nWhen you convert a conversation to a ticket, the following happens automatically:\\n\\n * The original conversation is moved to _Archived_ stage and cannot be reopened.\\n * A new ticket is created with: \\n * All internal discussions and customer messages copied from the conversation.\\n * Preserved", + "title": "Convert Conversations to Tickets | Conversations | Support | DevRev" }, { - "id": "ART-1979_KNOWLEDGE_NODE-45", - "text": "a user. In certain cases where the ticket depends on some fix (issues) the stage may go from *in development* to *awaiting customer response* when the corresponding issues have been resolved and the fix needs to be validated with the user.\\n\\n In certain cases, the customer experience engineer may be able to solve directly (without any required issues) which may change the stage from *work in progress* to *awaiting customer response* to validate they have solved the problem. If either has", - "title": "Tickets | Computer for Support Teams | DevRev" + "id": "ART-1981_KNOWLEDGE_NODE-30", + "text": "conversation of which you are not the owner, let the owner know to respond. It's beneficial to retain the same point of contact for the duration of the conversation unless the owner refers some another user.\\n* If the conversation has a customer org that's unidentified or is new, add yourself (the customer experience engineer) as the owner of the ticket. Try to find the appropriate owner for the customer org and update the customer record accordingly.\\n* Change the stage of the conversation to", + "title": "Support best practices | Computer for Support Teams | DevRev" }, { - "id": "ART-2012_KNOWLEDGE_NODE-28", - "text": "say \\xe2\\x80\\x9cI would like to add a terminal stage on my tickets\\xe2\\x80\\x9d and we will get it done.\\n\\n * If no terminal stage is set, tickets will reopen on new comments from customers if **Reopen Closed Tickets on customer message** is enabled in the [convergence snap-in](./converge). The tickets move to the _In Progress_ state by default.\\n\\n * If you connected your support email address with DevRev, it is recommended that you enable the **Allow automations to send email** in your", - "title": "Follow-up ticket | Automate | Snap-ins | DevRev" + "id": "ART-1645_KNOWLEDGE_NODE-45", + "text": ">| --header \\'Content-Type: application/json\\' \\\\ \\n >| --header \\'Authorization: Bearer \\' \\\\ \\n >| --data \\'{ \\n >| \"name\": \"Needs RCA\", \\n >| \"state\": \"closed\", \\n >| \"ordinal\": 1000 \\n >| }\\'\\n[/code] \\n \\nA stage can be referenced by any object type. For example, both _issue_ and _ticket_ object types can use the _in_development_ stage. It\\xe2\\x80\\x99s incorrect to say that the stage is bound to an _issue_ or _ticket_.\\n\\n### Create stage", + "title": "Object customization (Beta) \u2014 DevRev | Docs" }, { - "id": "ART-1979_KNOWLEDGE_NODE-42", - "text": "it's automatically put into the *queued* stage, which indicates that it needs to be picked up by a customer experience engineer.\\n\\n**In-progress**\\n\\n* *Work in progress* (WIP)\\n\\n Work on the concern reported by the user has begun. When a customer experience engineer starts work on a ticket, the ticket's stage changes to *work in progress*. When they require more information, they may ask the customer for additional detail (such as logs or context), in which case the stage would change to", - "title": "Tickets | Computer for Support Teams | DevRev" + "id": "ART-2011_KNOWLEDGE_NODE-5", + "text": "ticket conversion](/docs/product/conversation-ticket)\\n + [Tickets](/docs/product/tickets)\\n + [Routing](/docs/product/routing)\\n + [Support best practices](/docs/product/support-bp)\\n + [Customer portal](/docs/product/support-portal)\\n + [Questions & answers](/docs/product/qa)\\n + [Knowledge Base](/docs/product/knowledge-base)\\n\\n - [Articles](/docs/product/articles)\\n - [Collections](/docs/product/collection)\\n + [Turing AI agent](/docs/product/conversational-bot)\\n\\n - [Best", + "title": "CSAT on ticket | Automate | Snap-ins | DevRev" }, { - "id": "ART-2016_KNOWLEDGE_NODE-28", - "text": "depending on the message given by a discussion participant.\\n\\n Enter /StageConfig in the snap-in **Discussions** tab and select the values from the dropdown for the stage transition whenever a message is given by a discussion participant.\\n4. Go to **Issues** or **Roadmap** and make updates. The tickets that were linked to the issue or enhancement reflect the changes you configured in the CSV file, notifying the ticket owner.\\n\\n[PreviousSend customized", - "title": "StageFlow automator | Automate | Snap-ins | DevRev" + "id": "ART-2015_KNOWLEDGE_NODE-5", + "text": "ticket conversion](/docs/product/conversation-ticket)\\n + [Tickets](/docs/product/tickets)\\n + [Routing](/docs/product/routing)\\n + [Support best practices](/docs/product/support-bp)\\n + [Customer portal](/docs/product/support-portal)\\n + [Questions & answers](/docs/product/qa)\\n + [Knowledge Base](/docs/product/knowledge-base)\\n\\n - [Articles](/docs/product/articles)\\n - [Collections](/docs/product/collection)\\n + [Turing AI agent](/docs/product/conversational-bot)\\n\\n - [Best", + "title": "Descope identity validation | Automate | Snap-ins | DevRev" } ] }, @@ -4091,26 +4091,6 @@ "query_id": "eeedb1ab-bd3a-420d-b9a0-ecb2ce0e8835", "query": "Article 471 not viewable from internal and external links", "retrievals": [ - { - "id": "ART-15414_KNOWLEDGE_NODE-10", - "text": "elements exist.\\n\\n### Errors\\n\\n400\\n\\nBad Request Error\\n\\n401\\n\\nUnauthorized Error\\n\\n403\\n\\nForbidden Error\\n\\n429\\n\\nToo Many Requests Error\\n\\n500\\n\\nInternal Server Error\\n\\n503\\n\\nService Unavailable Error\\n\\nWas this page helpful?\\n\\nYesNo\\n\\n[Previous](/api-reference/links/list)[#### Replace Links\\n\\nNext](/api-reference/links/replace)[Built with](https://buildwithfern.com/?utm_campaign=buildWith&utm_medium=docs&utm_source=developer.devrev.ai)'", - "title": "List Links (POST) | DevRev | Docs" - }, - { - "id": "ART-1985_KNOWLEDGE_NODE-35", - "text": "and no longer required can be removed by archiving them.\\n\\nVisibility settings\\n-------------------\\n\\n### Article visibility\\n\\nTo control who can view the articles, open the **Visible to** menu. This displays all external groups that the article can be shared with. By default, the following groups are available:\\n\\n* **Customers**: Allows public access without verification.\\n\\n ![]()\\n\\n Public access requires the public portal to be enabled. If the public portal is not enabled, only", - "title": "Articles | Knowledge Base | Computer for Support Teams | DevRev" - }, - { - "id": "ART-15402_KNOWLEDGE_NODE-9", - "text": "elements exist.\\n\\n### Errors\\n\\n400\\n\\nBad Request Error\\n\\n401\\n\\nUnauthorized Error\\n\\n403\\n\\nForbidden Error\\n\\n429\\n\\nToo Many Requests Error\\n\\n500\\n\\nInternal Server Error\\n\\n503\\n\\nService Unavailable Error\\n\\nWas this page helpful?\\n\\nYesNo\\n\\n[Previous](/api-reference/links/get-post)[#### List Links (POST)\\n\\nNext](/api-reference/links/list-post)[Built with](https://buildwithfern.com/?utm_campaign=buildWith&utm_medium=docs&utm_source=developer.devrev.ai)'", - "title": "List Links | DevRev | Docs" - }, - { - "id": "ART-15404_KNOWLEDGE_NODE-7", - "text": "Error\\n\\n401\\n\\nUnauthorized Error\\n\\n403\\n\\nForbidden Error\\n\\n429\\n\\nToo Many Requests Error\\n\\n500\\n\\nInternal Server Error\\n\\n503\\n\\nService Unavailable Error\\n\\nWas this page helpful?\\n\\nYesNo\\n\\n[Previous](/api-reference/links/list-post)[#### Count Meetings\\n\\nNext](/api-reference/meetings/count)[Built with](https://buildwithfern.com/?utm_campaign=buildWith&utm_medium=docs&utm_source=developer.devrev.ai)'", - "title": "Replace Links | DevRev | Docs" - }, { "id": "ART-1985_KNOWLEDGE_NODE-38", "text": "and **Public Portal**.\\n\\n### Share an article\\n\\nOnce you've created an article, you have two options to share it:\\n\\n* Use **Copy external link** to share with your customers, allowing them to access the article directly.\\n* Use **Copy internal link** to share with your internal organizational team members.\\n\\nThe ability to view the article depends on the settings for **Visible to** and **Status** that have been configured.\\n\\n* If you are sharing an external link with non-signed-in", @@ -4122,9 +4102,14 @@ "title": "Articles | Knowledge Base | Computer for Support Teams | DevRev" }, { - "id": "ART-4070_KNOWLEDGE_NODE-1", - "text": "externalinternalprivatepublicrestricted\\n\\naliasesobjectOptional\\n\\nShow property\\n\\napplies_to_partsobjectOptional\\n\\nShow property\\n\\nartifactsobjectOptional\\n\\nShow property\\n\\nauthored_byobjectOptional\\n\\nShow property\\n\\nbrandstringOptional`format: \"id\"`\\n\\nThe updated brand of the article.\\n\\ncontent_blocksobjectOptional\\n\\nShow property\\n\\ncontent_formatenumOptional\\n\\nAllowed values: drdfv2rt\\n\\nContent format of the article.\\n\\ncustom_fieldsobjectOptional\\n\\nApplication-defined custom", - "title": "Update Article \u2014 DevRev | Docs" + "id": "ART-1985_KNOWLEDGE_NODE-35", + "text": "and no longer required can be removed by archiving them.\\n\\nVisibility settings\\n-------------------\\n\\n### Article visibility\\n\\nTo control who can view the articles, open the **Visible to** menu. This displays all external groups that the article can be shared with. By default, the following groups are available:\\n\\n* **Customers**: Allows public access without verification.\\n\\n ![]()\\n\\n Public access requires the public portal to be enabled. If the public portal is not enabled, only", + "title": "Articles | Knowledge Base | Computer for Support Teams | DevRev" + }, + { + "id": "ART-4092_KNOWLEDGE_NODE-2", + "text": "link\\xe2\\x80\\x99s information.\\n\\nlinkobject\\n\\nShow 9 properties\\n\\n### Errors\\n\\n400\\n\\nBad Request Error\\n\\n401\\n\\nUnauthorized Error\\n\\n403\\n\\nForbidden Error\\n\\n404\\n\\nNot Found Error\\n\\n429\\n\\nToo Many Requests Error\\n\\n500\\n\\nInternal Server Error\\n\\n503\\n\\nService Unavailable Error\\n\\nGET\\n\\n/links.get\\n\\n[code]\\n\\n $| curl -G https://api.devrev.ai/links.get \\\\ \\n ---|--- \\n >| -H \"Authorization: Bearer \" \\\\ \\n >| -d id=id\\n[/code] \\n \\nTry", + "title": "Get Link \u2014 DevRev | Docs" }, { "id": "ART-15297_KNOWLEDGE_NODE-9", @@ -4132,14 +4117,29 @@ "title": "Update Article | DevRev | Docs" }, { - "id": "ART-15410_KNOWLEDGE_NODE-2", - "text": "link.\\n\\n### Errors\\n\\n400\\n\\nBad Request Error\\n\\n401\\n\\nUnauthorized Error\\n\\n403\\n\\nForbidden Error\\n\\n404\\n\\nNot Found Error\\n\\n429\\n\\nToo Many Requests Error\\n\\n500\\n\\nInternal Server Error\\n\\n503\\n\\nService Unavailable Error\\n\\nWas this page helpful?\\n\\nYesNo\\n\\n[Previous](/api-reference/links/create)[#### Get Link\\n\\nNext](/api-reference/links/get)[Built with](https://buildwithfern.com/?utm_campaign=buildWith&utm_medium=docs&utm_source=developer.devrev.ai)'", - "title": "Delete Link | DevRev | Docs" + "id": "ART-1982_KNOWLEDGE_NODE-27", + "text": "visibility settings. Here are a few scenarios:\\n\\n* If a collection is not **Public**, none of the articles within it will be visible to customers, even if the articles are set to be **Visible to Customers**.\\n* If a collection is **Public**, only the articles set to be **Visible to Customers** will be publicly accessible. If an article within the public collection is configured with visibility for **Verified Customers**, non-signed-in customers won\\xe2\\x80\\x99t be able to view it.\\n* If a", + "title": "Collections | Knowledge Base | Computer for Support Teams | DevRev" }, { - "id": "ART-2141_KNOWLEDGE_NODE-9", - "text": "Error\\n\\n401\\n\\nUnauthorized Error\\n\\n403\\n\\nForbidden Error\\n\\n429\\n\\nToo Many Requests Error\\n\\n500\\n\\nInternal Server Error\\n\\n503\\n\\nService Unavailable Error\\n\\nWas this page helpful?\\n\\nYesNo\\n\\n[Previous](/beta/api-reference/customization/custom-link-type-list)[#### Update Link Types Custom\\n\\nNext](/beta/api-reference/customization/custom-link-type-update)[Built with](https://buildwithfern.com/?utm_campaign=buildWith&utm_medium=docs&utm_source=developer.devrev.ai)'", - "title": "List Link Types Custom (POST) | DevRev | Docs" + "id": "ART-1792_KNOWLEDGE_NODE-40", + "text": "article\\'s ID.\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\napplies_to_parts object Optional\\nShow property\\nartifacts object Optional\\nShow property\\nauthored_by object Optional\\nShow property\\ncustom_fields map from strings to any Optional\\nApplication-defined custom fields.\\ncustom_schema_spec object Optional\\nRequested custom schemas described abstractly. Every provided schema\\'s custom field must be specified, otherwise a bad request error is", + "title": "Update \u2014 DevRev | Docs" + }, + { + "id": "ART-1783_KNOWLEDGE_NODE-40", + "text": "article\\'s ID.\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\napplies_to_parts object Optional\\nShow property\\nartifacts object Optional\\nShow property\\nauthored_by object Optional\\nShow property\\ncustom_fields map from strings to any Optional\\nApplication-defined custom fields.\\ncustom_schema_spec object Optional\\nRequested custom schemas described abstractly. Every provided schema\\'s custom field must be specified, otherwise a bad request error is", + "title": "Locate \u2014 DevRev | Docs" + }, + { + "id": "ART-1823_KNOWLEDGE_NODE-40", + "text": "article\\'s ID.\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\napplies_to_parts object Optional\\nShow property\\nartifacts object Optional\\nShow property\\nauthored_by object Optional\\nShow property\\ncustom_fields map from strings to any Optional\\nApplication-defined custom fields.\\ncustom_schema_spec object Optional\\nRequested custom schemas described abstractly. Every provided schema\\'s custom field must be specified, otherwise a bad request error is", + "title": "Get \u2014 DevRev | Docs" + }, + { + "id": "ART-1605_KNOWLEDGE_NODE-40", + "text": "article\\'s ID.\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\napplies_to_parts object Optional\\nShow property\\nartifacts object Optional\\nShow property\\nauthored_by object Optional\\nShow property\\ncustom_fields map from strings to any Optional\\nApplication-defined custom fields.\\ncustom_schema_spec object Optional\\nRequested custom schemas described abstractly. Every provided schema\\'s custom field must be specified, otherwise a bad request error is", + "title": "Create \u2014 DevRev | Docs" } ] }, @@ -4148,54 +4148,54 @@ "query": "change Stage state in stage library", "retrievals": [ { - "id": "ART-3894_KNOWLEDGE_NODE-4", - "text": "14| \"transitions\": [ \\n 15| { \\n 16| \"target_stage\": { \\n 17| \"id\": \"foo\", \\n 18| \"display_id\": \"foo\", \\n 19| \"name\": \"foo\" \\n 20| } \\n 21| } \\n 22| ] \\n 23| } \\n 24| ], \\n 25| \"created_by\": { \\n 26| \"display_id\": \"foo\", \\n 27| \"id\": \"foo\", \\n 28| \"display_name\": \"foo\", \\n", - "title": "List Stage Diagrams (Beta) \u2014 DevRev | Docs" + "id": "ART-15353_KNOWLEDGE_NODE-5", + "text": "stage.\\n\\nstate\\\\_idstringOptional`format: \"id\"`\\n\\nThe state ID.\\n\\n### Response\\n\\nSuccess.\\n\\ncustom\\\\_stageobject\\n\\nShow 9 properties\\n\\n### Errors\\n\\n400\\n\\nBad Request Error\\n\\n401\\n\\nUnauthorized Error\\n\\n403\\n\\nForbidden Error\\n\\n404\\n\\nNot Found Error\\n\\n429\\n\\nToo Many Requests Error\\n\\n500\\n\\nInternal Server Error\\n\\n503\\n\\nService Unavailable Error\\n\\nWas this page helpful?\\n\\nYesNo\\n\\n[Previous](/api-reference/customization/custom-stages-list-post)[#### Create States", + "title": "Update Stages Custom | DevRev | Docs" }, { - "id": "ART-15345_KNOWLEDGE_NODE-1", - "text": "\" |\\n```\\n\\n[Try it](/api-reference/customization/stage-diagrams-list?explorer=true)\\n\\n200Retrieved\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | { |\\n| 2 | \"result\": [ |\\n| 3 | { |\\n| 4 | \"id\": \"string\", |\\n| 5 | \"stages\": [ |\\n| 6 | { |\\n| 7 | \"is_deprecated\": true, |\\n| 8 | \"is_start\": true, |\\n| 9 | \"stage\": { |\\n| 10 | \"id\": \"string\", |\\n| 11 | \"display_id\": \"string\", |\\n| 12 | \"name\": \"string\" |\\n| 13 | }, |\\n| 14 | \"transitions\": [ |\\n| 15 | { |\\n| 16 | \"target_stage\": { |\\n| 17 | \"id\":", - "title": "List Stage Diagrams | DevRev | Docs" + "id": "ART-1509_KNOWLEDGE_NODE-233", + "text": "Optional\\nThe state ID.\\nResponse.\\n\\nThis endpoint returns an object.\\ncustom_stage object\\nShow 9 properties\\nAPI Reference customization Custom States Create.\\n\\nPOST https:// api.devrev.ai / states.custom.create\\nCreates a custom state.\\nRequest.\\n\\nThis endpoint expects an object.\\nname string Required\\nThe name of the custom state.\\nordinal integer Required\\nOrdinal of the custom state used to identify system states.\\nis_final boolean Optional\\nWhether this is a final", + "title": "Prepare \u2014 DevRev | Docs" }, { - "id": "ART-15354_KNOWLEDGE_NODE-2", - "text": "\"name\": \"string\" |\\n| 13 | }, |\\n| 14 | \"transitions\": [ |\\n| 15 | { |\\n| 16 | \"target_stage\": { |\\n| 17 | \"id\": \"string\", |\\n| 18 | \"display_id\": \"string\", |\\n| 19 | \"name\": \"string\" |\\n| 20 | } |\\n| 21 | } |\\n| 22 | ] |\\n| 23 | } |\\n| 24 | ], |\\n| 25 | \"created_by\": { |\\n| 26 | \"display_id\": \"string\", |\\n| 27 | \"id\": \"string\", |\\n| 28 | \"display_name\": \"string\", |\\n| 29 | \"display_picture\": { |\\n| 30 | \"display_id\": \"string\", |\\n| 31 | \"id\": \"string\", |\\n| 32 | \"file\": { |\\n| 33 | \"type\":", - "title": "List Stage Diagrams (POST) | DevRev | Docs" + "id": "ART-1651_KNOWLEDGE_NODE-231", + "text": "Optional\\nThe state ID.\\nResponse.\\n\\nThis endpoint returns an object.\\ncustom_stage object\\nShow 9 properties\\nAPI Reference customization Custom States Create.\\n\\nPOST https:// api.devrev.ai / states.custom.create\\nCreates a custom state.\\nRequest.\\n\\nThis endpoint expects an object.\\nname string Required\\nThe name of the custom state.\\nordinal integer Required\\nOrdinal of the custom state used to identify system states.\\nis_final boolean Optional\\nWhether this is a final", + "title": "Create \u2014 DevRev | Docs" }, { - "id": "ART-3893_KNOWLEDGE_NODE-4", - "text": "\\n 5| { \\n 6| \"is_deprecated\": true, \\n 7| \"is_start\": true, \\n 8| \"stage\": { \\n 9| \"id\": \"foo\", \\n 10| \"display_id\": \"foo\", \\n 11| \"name\": \"foo\" \\n 12| }, \\n 13| \"transitions\": [ \\n 14| { \\n 15| \"target_stage\": { \\n 16| \"id\": \"foo\", \\n 17| \"display_id\": \"foo\", \\n 18| \"name\": \"foo\" \\n 19|", - "title": "Get Stage Diagram (Beta) \u2014 DevRev | Docs" + "id": "ART-1595_KNOWLEDGE_NODE-231", + "text": "Optional\\nThe state ID.\\nResponse.\\n\\nThis endpoint returns an object.\\ncustom_stage object\\nShow 9 properties\\nAPI Reference customization Custom States Create.\\n\\nPOST https:// api.devrev.ai / states.custom.create\\nCreates a custom state.\\nRequest.\\n\\nThis endpoint expects an object.\\nname string Required\\nThe name of the custom state.\\nordinal integer Required\\nOrdinal of the custom state used to identify system states.\\nis_final boolean Optional\\nWhether this is a final", + "title": "List \u2014 DevRev | Docs" }, { - "id": "ART-15350_KNOWLEDGE_NODE-2", - "text": "\"is_deprecated\": true, |\\n| 7 | \"is_start\": true, |\\n| 8 | \"stage\": { |\\n| 9 | \"id\": \"string\", |\\n| 10 | \"display_id\": \"string\", |\\n| 11 | \"name\": \"string\" |\\n| 12 | }, |\\n| 13 | \"transitions\": [ |\\n| 14 | { |\\n| 15 | \"target_stage\": { |\\n| 16 | \"id\": \"string\", |\\n| 17 | \"display_id\": \"string\", |\\n| 18 | \"name\": \"string\" |\\n| 19 | } |\\n| 20 | } |\\n| 21 | ] |\\n| 22 | } |\\n| 23 | ], |\\n| 24 | \"created_by\": { |\\n| 25 | \"display_id\": \"string\", |\\n| 26 | \"id\": \"string\", |\\n| 27 | \"display_name\":", - "title": "Create Stage Diagram | DevRev | Docs" + "id": "ART-1649_KNOWLEDGE_NODE-231", + "text": "Optional\\nThe state ID.\\nResponse.\\n\\nThis endpoint returns an object.\\ncustom_stage object\\nShow 9 properties\\nAPI Reference customization Custom States Create.\\n\\nPOST https:// api.devrev.ai / states.custom.create\\nCreates a custom state.\\nRequest.\\n\\nThis endpoint expects an object.\\nname string Required\\nThe name of the custom state.\\nordinal integer Required\\nOrdinal of the custom state used to identify system states.\\nis_final boolean Optional\\nWhether this is a final", + "title": "Create \u2014 DevRev | Docs" }, { - "id": "ART-15353_KNOWLEDGE_NODE-5", - "text": "stage.\\n\\nstate\\\\_idstringOptional`format: \"id\"`\\n\\nThe state ID.\\n\\n### Response\\n\\nSuccess.\\n\\ncustom\\\\_stageobject\\n\\nShow 9 properties\\n\\n### Errors\\n\\n400\\n\\nBad Request Error\\n\\n401\\n\\nUnauthorized Error\\n\\n403\\n\\nForbidden Error\\n\\n404\\n\\nNot Found Error\\n\\n429\\n\\nToo Many Requests Error\\n\\n500\\n\\nInternal Server Error\\n\\n503\\n\\nService Unavailable Error\\n\\nWas this page helpful?\\n\\nYesNo\\n\\n[Previous](/api-reference/customization/custom-stages-list-post)[#### Create States", - "title": "Update Stages Custom | DevRev | Docs" + "id": "ART-1650_KNOWLEDGE_NODE-231", + "text": "Optional\\nThe state ID.\\nResponse.\\n\\nThis endpoint returns an object.\\ncustom_stage object\\nShow 9 properties\\nAPI Reference customization Custom States Create.\\n\\nPOST https:// api.devrev.ai / states.custom.create\\nCreates a custom state.\\nRequest.\\n\\nThis endpoint expects an object.\\nname string Required\\nThe name of the custom state.\\nordinal integer Required\\nOrdinal of the custom state used to identify system states.\\nis_final boolean Optional\\nWhether this is a final", + "title": "List Post \u2014 DevRev | Docs" }, { - "id": "ART-3895_KNOWLEDGE_NODE-3", - "text": "\"is_start\": true, \\n 8| \"stage\": { \\n 9| \"id\": \"foo\", \\n 10| \"display_id\": \"foo\", \\n 11| \"name\": \"foo\" \\n 12| }, \\n 13| \"transitions\": [ \\n 14| { \\n 15| \"target_stage\": { \\n 16| \"id\": \"foo\", \\n 17| \"display_id\": \"foo\", \\n 18| \"name\": \"foo\" \\n 19| } \\n 20| } \\n 21| ] \\n 22| } \\n", - "title": "Update Stage Diagram (Beta) \u2014 DevRev | Docs" + "id": "ART-1605_KNOWLEDGE_NODE-231", + "text": "Optional\\nThe state ID.\\nResponse.\\n\\nThis endpoint returns an object.\\ncustom_stage object\\nShow 9 properties\\nAPI Reference customization Custom States Create.\\n\\nPOST https:// api.devrev.ai / states.custom.create\\nCreates a custom state.\\nRequest.\\n\\nThis endpoint expects an object.\\nname string Required\\nThe name of the custom state.\\nordinal integer Required\\nOrdinal of the custom state used to identify system states.\\nis_final boolean Optional\\nWhether this is a final", + "title": "Create \u2014 DevRev | Docs" }, { - "id": "ART-3898_KNOWLEDGE_NODE-8", - "text": "}\\n[/code] \\n \\n[Update Stage DiagramUp Next](/beta/api-reference/customization/stage-diagrams-update)\\n\\n[Built with](https://buildwithfern.com/?utm_campaign=buildWith&utm_medium=docs&utm_source=developer.devrev.ai)\\n\\n[Enterprise grade security to protect customer dataLearn more about it.](https://devrev.ai/blog/soc-compliance)\\n\\nProduct\\n\\n * [Build](https://devrev.ai/build)\\n * [Support](https://devrev.ai/support)\\n * [Search](https://devrev.ai/search)\\n * [PLuG - User", - "title": "List Stage Diagrams (POST) (Beta) \u2014 DevRev | Docs" + "id": "ART-1826_KNOWLEDGE_NODE-231", + "text": "Optional\\nThe state ID.\\nResponse.\\n\\nThis endpoint returns an object.\\ncustom_stage object\\nShow 9 properties\\nAPI Reference customization Custom States Create.\\n\\nPOST https:// api.devrev.ai / states.custom.create\\nCreates a custom state.\\nRequest.\\n\\nThis endpoint expects an object.\\nname string Required\\nThe name of the custom state.\\nordinal integer Required\\nOrdinal of the custom state used to identify system states.\\nis_final boolean Optional\\nWhether this is a final", + "title": "Get Post \u2014 DevRev | Docs" }, { - "id": "ART-3894_KNOWLEDGE_NODE-14", - "text": "__\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](https://devrev.ai/request-a-demo)\\n\\n[](https://devrev.ai)\\n\\n __\\n\\nProduct __\\n\\nPlatform __\\n\\nSolutions __\\n\\nMarketplace __\\n\\nCompany __\\n\\nResources __\\n\\n[Pricing](https://devrev.ai/pricing)\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](https://devrev.ai/request-a-demo)\\n\\n'", - "title": "List Stage Diagrams (Beta) \u2014 DevRev | Docs" + "id": "ART-1835_KNOWLEDGE_NODE-231", + "text": "Optional\\nThe state ID.\\nResponse.\\n\\nThis endpoint returns an object.\\ncustom_stage object\\nShow 9 properties\\nAPI Reference customization Custom States Create.\\n\\nPOST https:// api.devrev.ai / states.custom.create\\nCreates a custom state.\\nRequest.\\n\\nThis endpoint expects an object.\\nname string Required\\nThe name of the custom state.\\nordinal integer Required\\nOrdinal of the custom state used to identify system states.\\nis_final boolean Optional\\nWhether this is a final", + "title": "List \u2014 DevRev | Docs" }, { - "id": "ART-3898_KNOWLEDGE_NODE-4", - "text": "11| \"display_id\": \"foo\", \\n 12| \"name\": \"foo\" \\n 13| }, \\n 14| \"transitions\": [ \\n 15| { \\n 16| \"target_stage\": { \\n 17| \"id\": \"foo\", \\n 18| \"display_id\": \"foo\", \\n 19| \"name\": \"foo\" \\n 20| } \\n 21| } \\n 22| ] \\n 23| } \\n 24| ], \\n 25| \"created_by\": { \\n 26|", - "title": "List Stage Diagrams (POST) (Beta) \u2014 DevRev | Docs" + "id": "ART-15344_KNOWLEDGE_NODE-1", + "text": "|\\n```\\n\\n[Try it](/api-reference/customization/stage-diagrams-get?explorer=true)\\n\\n200Retrieved\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | { |\\n| 2 | \"stage_diagram\": { |\\n| 3 | \"id\": \"string\", |\\n| 4 | \"stages\": [ |\\n| 5 | { |\\n| 6 | \"is_deprecated\": true, |\\n| 7 | \"is_start\": true, |\\n| 8 | \"stage\": { |\\n| 9 | \"id\": \"string\", |\\n| 10 | \"display_id\": \"string\", |\\n| 11 | \"name\": \"string\" |\\n| 12 | }, |\\n| 13 | \"transitions\": [ |\\n| 14 | { |\\n| 15 | \"target_stage\": { |\\n| 16 | \"id\": \"string\", |\\n|", + "title": "Get Stage Diagram | DevRev | Docs" } ] }, @@ -4205,53 +4205,53 @@ "retrievals": [ { "id": "ART-16804_KNOWLEDGE_NODE-27", - "text": "already exists, you can reuse it; otherwise, click **Add\\n Connection**. \\n In the connection modal, click **Sign in with snap-in** (with the Google\\n Calendar icon), enter a connection name, and proceed to **authorize via your\\n Google account using OAuth**. \\n Provide the necessary permissions and click **Continue** to complete the\\n setup.\\n5. Once the connection is established, select the calendars you want to import\\n and specify the DevRev part that should be used for any", + "text": "already exists, you can reuse it; otherwise, click **Add\\n Connection**. \\n In the connection modal, click **Sign in with snap-in** (with the Google\\n Calendar icon), enter a connection name, and proceed to **authorize via your\\n Google account using OAuth**. \\n Provide the necessary permissions and click **Continue** to complete the\\n setup.\\n5. Once the connection is established, select the calendars you want to import\\n and specify the DevRev part that should be used for any", "title": "Google Calendar AirSync | Integrate | Snap-ins | DevRev" }, { - "id": "ART-16804_KNOWLEDGE_NODE-26", - "text": "Identities | \\xe2\\x9c\\x85 |\\n| Meetings | Meetings | \\xe2\\x9c\\x85 |\\n\\nImport Google Calendar\\n----------------------\\n\\nFollow the steps below to import from Google Calendar:\\n\\n1. Go to the **Marketplace** and search for **Google Calendar** in the\\n **Import** category, and install.\\n2. Go to the **Import** section in your settings left nav.\\n3. Click **+Import** and select the Google Calendar logo.\\n4. In the **Select Connection** dropdown, choose **Google Calendar**. \\n If a connection", - "title": "Google Calendar AirSync | Integrate | Snap-ins | DevRev" + "id": "ART-2032_KNOWLEDGE_NODE-26", + "text": "section within your DevRev workspace settings.\\n2. Click **Explore Marketplace**.\\n3. Search for **Google Calendar** and click **Install** next to the Google Calendar snap-in.\\n4. In DevRev app, setup the connection in **Settings** > **Snap-ins** > **Connections** on top.\\n\\n * Search and choose an existing connection or create a new one by clicking **+ Connection**.\\n * Select **Google Calendar** from the dowpdown list.\\n * Give it a name and sign in with Google Calendar. Ensure to", + "title": "Google Calendar | Integrate | Snap-ins | DevRev" }, { - "id": "ART-3207_KNOWLEDGE_NODE-28", - "text": "In the top-right corner, select **+ Connection**, choose Google, and enter your connection name and domain name.\\n3. Toggle on **Make public** to make the connection public for your organization and click **Next**.\\n4. Click **Sign in with Google** and add your organization\\xe2\\x80\\x99s Gmail account. If you are already logged in using a different Gmail account select **Use another account** and continue.\\n\\n If you are using Google Groups then use the same Gmail account which has permission", - "title": "Email snap-in configuration | Email | Integrate | Snap-ins | DevRev" + "id": "ART-1283_KNOWLEDGE_NODE-1", + "text": "information, refer to Keyrings in the snap-in manifest. They can be categorized into two main types:\\n\\nDefault keyrings. :\\n\\nOrganization scoped keyrings. : These are secrets used by the entire organization, for example, a Slack token for a workspace.\\nUser scoped keyrings. : These are secrets for a single user, for example, the token to interact with a single person\\xe2\\x80\\x99s Google Calendar.\\n\\nDuring installation, the user will be prompted to provide credentials for each keyring.\\n\\n1", + "title": "Keyrings \u2014 DevRev | Docs" }, { - "id": "ART-2032_KNOWLEDGE_NODE-26", - "text": "section within your DevRev workspace settings.\\n2. Click **Explore Marketplace**.\\n3. Search for **Google Calendar** and click **Install** next to the Google Calendar snap-in.\\n4. In DevRev app, setup the connection in **Settings** > **Snap-ins** > **Connections** on top.\\n\\n * Search and choose an existing connection or create a new one by clicking **+ Connection**.\\n * Select **Google Calendar** from the dowpdown list.\\n * Give it a name and sign in with Google Calendar. Ensure to", - "title": "Google Calendar | Integrate | Snap-ins | DevRev" + "id": "ART-1491_KNOWLEDGE_NODE-1", + "text": "information, refer to Keyrings in the snap-in manifest. They can be categorized into two main types:\\n\\nDefault keyrings. :\\n\\nOrganization scoped keyrings. : These are secrets used by the entire organization, for example, a Slack token for a workspace.\\nUser scoped keyrings. : These are secrets for a single user, for example, the token to interact with a single person\\xe2\\x80\\x99s Google Calendar.\\n\\nDuring installation, the user will be prompted to provide credentials for each keyring.\\n\\n1", + "title": "Keyrings \u2014 DevRev | Docs" }, { - "id": "ART-3207_KNOWLEDGE_NODE-27", - "text": "connection\\n--------------------------\\n\\nIf you are using Google as the mail provider, refer to **Gmail connection**; if you are using custom domains or other providers, refer to **Email connection**.\\n\\nGmail connection\\n\\nYou must be a part of the group and have permission to send emails to the Google Group. This approach doesn\\'t work with generic Google Groups ending with @googlegroups.com.\\n\\n1. In the DevRev app, go to **Settings > Integrations > Snap-ins** and click **Connections**.\\n2.", - "title": "Email snap-in configuration | Email | Integrate | Snap-ins | DevRev" + "id": "ART-2032_KNOWLEDGE_NODE-30", + "text": "sync\\n\\n1. Update the snap-in configurations as needed.\\n\\n * **Calendar ID**: ID of Google calendar to be synced with DevRev. The default is primary.\\n * **Exclude Matching Events**: Excludes event if their title starts or ends with the specified string. Default is -.\\n * **Skip Events With Emails**: Events containing any of these email addresses are completely excluded from sync. No meetings are created in DevRev for events where these emails appear as attendees, organizers, or", + "title": "Google Calendar | Integrate | Snap-ins | DevRev" }, { "id": "ART-2032_KNOWLEDGE_NODE-27", - "text": "toggle on **Make public** to make the connection public for your organization.\\n\\n#### Organization calendar sync\\n\\n1. Update the snap-in configurations as needed.\\n\\n * **Internal Domains**: List of internal domains to be considered as internal users.\\n * **Calendar ID**: ID of Google calendar to be synced to DevRev. The default is primary.\\n * **Exclude Matching Events**: Excludes event if their title starts or ends with the specified string. Default is -.\\n * **Skip Events With", + "text": "toggle on **Make public** to make the connection public for your organization.\\n\\n#### Organization calendar sync\\n\\n1. Update the snap-in configurations as needed.\\n\\n * **Internal Domains**: List of internal domains to be considered as internal users.\\n * **Calendar ID**: ID of Google calendar to be synced to DevRev. The default is primary.\\n * **Exclude Matching Events**: Excludes event if their title starts or ends with the specified string. Default is -.\\n * **Skip Events With", "title": "Google Calendar | Integrate | Snap-ins | DevRev" }, { - "id": "ART-2032_KNOWLEDGE_NODE-29", - "text": "as customers.\\n\\n* **Track meetings from free email domains**: Enable this feature to capture meetings scheduled by non-work email addresses, such as those from gmail.com or yahoo.com.\\n* **Recurring days**: Number of days in advance for recurring events to be synced. Default is 7 days.\\n\\n The recurring events inside the specified advance days are created, that is, if 7 days is specified, then all recurring events in next 7 days are created.\\n\\n1. Install the snap-in.\\n\\n#### User calendar", - "title": "Google Calendar | Integrate | Snap-ins | DevRev" + "id": "ART-2666_KNOWLEDGE_NODE-16", + "text": "* [Google Calendar](/docs/integrations/google-calendar)\\n * [Email](/docs/integrations/email)\\n\\n * [Email snap-in configuration](/docs/integrations/email-config)\\n\\n * [Exotel](/docs/integrations/exotel)\\n * [Slack](/docs/integrations/slack)\\n * [WhatsApp](/docs/integrations/whatsapp)\\n * [GitHub](/docs/integrations/github)\\n * [GitLab](/docs/integrations/gitlab)\\n * [Harness](/docs/integrations/harness)\\n *", + "title": "October 5: Left navigation | Changelog | DevRev" }, { - "id": "ART-2025_KNOWLEDGE_NODE-26", - "text": "**Explore Marketplace**.\\n3. Search for **Calendly** and click **Install** next to the Calendly snap-in.\\n4. In DevRev app, setup the connection in **Settings** > **Snap-ins** > **Connections** on top.\\n\\n * Search and choose an existing connection or create a new one by clicking **+ Connection**.\\n * Select **Snap-In Secret** from the dowpdown list.\\n * Give it a name and paste your Calendly personal access token in the **Secret** field. Toggle on **Make public** if you want to make the", - "title": "Calendly | Integrate | Snap-ins | DevRev" + "id": "ART-16804_KNOWLEDGE_NODE-0", + "text": "b'Google Calendar AirSync | Integrate | Snap-ins | DevRev\\n\\n* Computer\\n* Resources\\n* [Our Customers](/case-study)\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](/request-a-demo)\\n\\nComputer\\n\\nResources\\n\\n[Our Customers](/case-study)\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](/request-a-demo)\\n\\nSearch\\n\\n`CMD`\\xc2\\xa0+\\xc2\\xa0`K`\\n\\n* [Introduction](/docs)\\n* [Computer by DevRev](/docs/intro)\\n\\n + [Core concepts](/docs/product/core)\\n + [Apps](/docs/product/apps)\\n +", + "title": "Google Calendar AirSync | Integrate | Snap-ins | DevRev" }, { - "id": "ART-2032_KNOWLEDGE_NODE-16", - "text": "snap-in configuration](/docs/integrations/email-config)\\n - [Exotel](/docs/integrations/exotel)\\n - [Slack](/docs/integrations/slack)\\n - [WhatsApp](/docs/integrations/whatsapp)\\n - [GitHub](/docs/integrations/github)\\n - [GitLab](/docs/integrations/gitlab)\\n - [Harness](/docs/integrations/harness)\\n - [Marker.io](/docs/integrations/marker-io)\\n - [Instabug](/docs/integrations/instabug)\\n - [Qase](/docs/integrations/qase)\\n - [Tracxn", + "id": "ART-2032_KNOWLEDGE_NODE-0", + "text": "b\"Google Calendar | Integrate | Snap-ins | DevRev\\n\\n* Product\\n* Platform\\n* Marketplace\\n* Company\\n* Resources\\n* Pricing\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](/request-a-demo)\\n\\nProduct\\n\\nPlatform\\n\\nMarketplace\\n\\nCompany\\n\\nResources\\n\\nPricing\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](/request-a-demo)\\n\\nSearch\\n\\n`CTRL`\\xc2\\xa0+\\xc2\\xa0`K`\\n\\n* [Introduction](/docs)\\n* [AgentOS platform](/docs/intro)\\n\\n + [Core concepts](/docs/product/core)\\n +", "title": "Google Calendar | Integrate | Snap-ins | DevRev" }, { - "id": "ART-16804_KNOWLEDGE_NODE-33", - "text": "Sync](#set-up-periodic-sync)\\n* [Delete an import](#delete-an-import)\\n\\n[Enterprise grade security to protect customer data\\n\\nLearn more about it.\\n\\n![]()](/blog/soc-compliance)\\n\\nComputer\\n\\n* [Meet Computer](/meet-computer)\\n* [How Computer works](/how-computer-works)\\n\\nApps\\n\\n* [For Support Teams](/for-support-teams)\\n* [For Builders](/for-builders)\\n* [For Customers](/for-customers)\\n* [For User Insights](/for-user-insights)\\n*", - "title": "Google Calendar AirSync | Integrate | Snap-ins | DevRev" + "id": "ART-4271_KNOWLEDGE_NODE-14", + "text": "* [Google Calendar](/docs/integrations/google-calendar?)\\n * [Email](/docs/integrations/email?)\\n\\n * [Email snap-in configuration](/docs/integrations/email-config?)\\n\\n * [Exotel](/docs/integrations/exotel?)\\n * [Slack](/docs/integrations/slack?)\\n * [WhatsApp](/docs/integrations/whatsapp?)\\n * [GitHub](/docs/integrations/github?)\\n * [Harness](/docs/integrations/harness?)\\n * [Marker.io](/docs/integrations/marker-io?)\\n *", + "title": "Convert Conversations to Tickets | Conversations | Support | DevRev" } ] }, @@ -4261,18 +4261,18 @@ "retrievals": [ { "id": "ART-15664_KNOWLEDGE_NODE-6", - "text": "you want to establish a parent-child relationship between tickets and a custom object\\ntype called \\xe2\\x80\\x9cCampaign\\xe2\\x80\\x9d. This relationship helps track which tickets are assigned to which campaigns.\\n\\nTo create this relationship, make an API call to create a link type:\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl --location \\'https://api.devrev.ai/link-types.custom.create\\' \\\\ |\\n| > | --header \\'Content-Type: application/json\\' \\\\ |\\n| > | --header \\'Authorization: Bearer \\'", + "text": "you want to establish a parent-child relationship between tickets and a custom object\\ntype called \\xe2\\x80\\x9cCampaign\\xe2\\x80\\x9d. This relationship helps track which tickets are assigned to which campaigns.\\n\\nTo create this relationship, make an API call to create a link type:\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl --location \\'https://api.devrev.ai/link-types.custom.create\\' \\\\ |\\n| > | --header \\'Content-Type: application/json\\' \\\\ |\\n| > | --header \\'Authorization: Bearer \\'", "title": "Links | DevRev | Docs" }, { - "id": "ART-15664_KNOWLEDGE_NODE-8", - "text": "created from (ticket)\\n* Target types that the link can be created to (campaign custom object)\\n* Forward name (\\xe2\\x80\\x9cis parent of\\xe2\\x80\\x9d) describing the relationship from ticket to campaign\\n* Backward name (\\xe2\\x80\\x9cis child of\\xe2\\x80\\x9d) describing the relationship from campaign to ticket\\n\\nCreate links between objects\\n----------------------------\\n\\nOnce you have defined a link type, you can create links between objects:\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl", - "title": "Links | DevRev | Docs" + "id": "ART-1556_KNOWLEDGE_NODE-4", + "text": "object=object\\n[/code] \\n \\nTry it\\n\\n200Retrieved\\n\\n[code]\\n\\n 1| { \\n ---|--- \\n 2| \"links\": [ \\n 3| { \\n 4| \"id\": \"id\", \\n 5| \"link_type\": \"custom_link\", \\n 6| \"source\": { \\n 7| \"type\": \"ticket\", \\n 8| \"id\": \"source\", \\n 9| \"owned_by\": [ \\n 10| { \\n 11| \"type\": \"sys_user\", \\n 12| \"id\": \"source\" \\n 13| } \\n 14| ], \\n 15|", + "title": "List Links (Beta) \u2014 DevRev | Docs" }, { - "id": "ART-12390_KNOWLEDGE_NODE-39", - "text": "to update * subtype: (Optional) Ticket subtype * apps: (Optional) Related apps * app\\\\_custom\\\\_fields: (Optional) Custom fields * stage: (Optional) New stage | Updated ticket object |\\n\\nObject links\\n------------\\n\\n| Operation | Description | Input Parameters | Output |\\n| --- | --- | --- | --- |\\n| LinkConversationWithTicket | Creates a link between a conversation and a ticket. | * source: Conversation ID * link\\\\_type: Type of link (usually \"is\\\\_related\\\\_to\") * target: Ticket ID | Empty", - "title": "Workflow action library | Workflows | Computer by DevRev | DevRev" + "id": "ART-15664_KNOWLEDGE_NODE-8", + "text": "created from (ticket)\\n* Target types that the link can be created to (campaign custom object)\\n* Forward name (\\xe2\\x80\\x9cis parent of\\xe2\\x80\\x9d) describing the relationship from ticket to campaign\\n* Backward name (\\xe2\\x80\\x9cis child of\\xe2\\x80\\x9d) describing the relationship from campaign to ticket\\n\\nCreate links between objects\\n----------------------------\\n\\nOnce you have defined a link type, you can create links between objects:\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl", + "title": "Links | DevRev | Docs" }, { "id": "ART-15664_KNOWLEDGE_NODE-5", @@ -4280,34 +4280,34 @@ "title": "Links | DevRev | Docs" }, { - "id": "ART-15664_KNOWLEDGE_NODE-16", - "text": "\\'https://api.devrev.ai/link-types.custom.update\\' \\\\ |\\n| > | --header \\'Content-Type: application/json\\' \\\\ |\\n| > | --header \\'Authorization: Bearer \\' \\\\ |\\n| > | --data \\'{ |\\n| > | \"id\": \"don:core:dvrv-us-1:devo/demo:custom_link_type/1\", |\\n| > | \"is_deprecated\": true |\\n| > | }\\' |\\n```\\n\\nQuick reference: links from tickets, and issues\\n-----------------------------------------------\\n\\n##### \\n\\nThis section lists common links you can create from tickets and issues. It is not an", + "id": "ART-15664_KNOWLEDGE_NODE-13", + "text": "\\n\\nYou may want to restrict links to specific subtypes of objects. For example, only allowing issues\\nof a particular subtype to be linked to tickets.\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl --location \\'https://api.devrev.ai/link-types.custom.create\\' \\\\ |\\n| > | --header \\'Content-Type: application/json\\' \\\\ |\\n| > | --header \\'Authorization: Bearer \\' \\\\ |\\n| > | --data \\'{ |\\n| > | \"name\": \"Link between social media issues and tickets\", |\\n| > | \"source_types\": [ |\\n| > | { |\\n|", "title": "Links | DevRev | Docs" }, { - "id": "ART-15664_KNOWLEDGE_NODE-13", - "text": "\\n\\nYou may want to restrict links to specific subtypes of objects. For example, only allowing issues\\nof a particular subtype to be linked to tickets.\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl --location \\'https://api.devrev.ai/link-types.custom.create\\' \\\\ |\\n| > | --header \\'Content-Type: application/json\\' \\\\ |\\n| > | --header \\'Authorization: Bearer \\' \\\\ |\\n| > | --data \\'{ |\\n| > | \"name\": \"Link between social media issues and tickets\", |\\n| > | \"source_types\": [ |\\n| > | { |\\n|", - "title": "Links | DevRev | Docs" + "id": "ART-1552_KNOWLEDGE_NODE-2", + "text": "\"target\" \\n >| }\\'\\n[/code] \\n \\nTry it\\n\\n201Created\\n\\n[code]\\n\\n 1| { \\n ---|--- \\n 2| \"link\": { \\n 3| \"id\": \"id\", \\n 4| \"link_type\": \"custom_link\", \\n 5| \"source\": { \\n 6| \"type\": \"ticket\", \\n 7| \"id\": \"source\", \\n 8| \"owned_by\": [ \\n 9| { \\n 10| \"type\": \"sys_user\", \\n 11| \"id\": \"source\" \\n 12| } \\n 13| ], \\n 14| \"title\": \"source\", \\n 15|", + "title": "Create Link (Beta) \u2014 DevRev | Docs" }, { - "id": "ART-15664_KNOWLEDGE_NODE-12", - "text": "application/json\\' \\\\ |\\n| > | --header \\'Authorization: Bearer \\' \\\\ |\\n| > | --data \\'{ |\\n| > | \"id\": \"don:core:dvrv-us-1:devo/demo:custom_link_type/1\", |\\n| > | \"name\": \"Link type between issue/ticket and campaign\", |\\n| > | \"source_types_v2\": [ |\\n| > | { |\\n| > | \"leaf_type\": \"issue\" |\\n| > | }, |\\n| > | { |\\n| > | \"leaf_type\": \"ticket\" |\\n| > | } |\\n| > | ] |\\n| > | }\\' |\\n```\\n\\nCreate links between objects with subtypes\\n------------------------------------------\\n\\n#####", + "id": "ART-15664_KNOWLEDGE_NODE-16", + "text": "\\'https://api.devrev.ai/link-types.custom.update\\' \\\\ |\\n| > | --header \\'Content-Type: application/json\\' \\\\ |\\n| > | --header \\'Authorization: Bearer \\' \\\\ |\\n| > | --data \\'{ |\\n| > | \"id\": \"don:core:dvrv-us-1:devo/demo:custom_link_type/1\", |\\n| > | \"is_deprecated\": true |\\n| > | }\\' |\\n```\\n\\nQuick reference: links from tickets, and issues\\n-----------------------------------------------\\n\\n##### \\n\\nThis section lists common links you can create from tickets and issues. It is not an", "title": "Links | DevRev | Docs" }, { - "id": "ART-2139_KNOWLEDGE_NODE-0", - "text": "b'Create Link Types Custom | DevRev | Docs\\n\\n[![]()![]()](https://developer.devrev.ai/)\\n\\nBeta\\n\\nBeta\\n\\nBeta\\n\\nSearch\\n\\n`/`\\n\\n[API Reference](/beta/api-reference/accounts/create)[customization](/beta/api-reference/customization/custom-objects-count)\\n\\nCreate Link Types Custom\\n========================\\n\\nBeta\\n\\nCopy page\\n\\nPOST\\n\\nhttps://api.devrev.ai/link-types.custom.create\\n\\nPOST\\n\\n/link-types.custom.create\\n\\ncURL\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl -X POST", - "title": "Create Link Types Custom | DevRev | Docs" + "id": "ART-1543_KNOWLEDGE_NODE-121", + "text": "object.\\n\\ntitle string Optional\\n\\nUpdates the title of the custom object.\\n\\nResponse.\\n\\nThis endpoint returns an object.\\ncustom_object object\\nShow 10 properties\\nAPI Reference customization Custom Link Type Create.\\n\\nPOST https://api.devrev.ai / link-types.custom.create\\n\\nCreates a custom link type.\\n\\nRequest.\\n\\nThis endpoint expects an object.\\nbackward_name string Required\\n\\nThe name of the link in the backward direction.\\n\\nforward_name string Required\\n\\nThe name of the link in", + "title": "Metric Definitions List Post (Beta) \u2014 DevRev | Docs" }, { - "id": "ART-2139_KNOWLEDGE_NODE-8", - "text": "helpful?\\n\\nYesNo\\n\\n[Previous](/beta/api-reference/customization/custom-objects-update)[#### Get Link Types Custom\\n\\nNext](/beta/api-reference/customization/custom-link-type-get)[Built with](https://buildwithfern.com/?utm_campaign=buildWith&utm_medium=docs&utm_source=developer.devrev.ai)'", - "title": "Create Link Types Custom | DevRev | Docs" + "id": "ART-1545_KNOWLEDGE_NODE-121", + "text": "object.\\n\\ntitle string Optional\\n\\nUpdates the title of the custom object.\\n\\nResponse.\\n\\nThis endpoint returns an object.\\ncustom_object object\\nShow 10 properties\\nAPI Reference customization Custom Link Type Create.\\n\\nPOST https://api.devrev.ai / link-types.custom.create\\n\\nCreates a custom link type.\\n\\nRequest.\\n\\nThis endpoint expects an object.\\nbackward_name string Required\\n\\nThe name of the link in the backward direction.\\n\\nforward_name string Required\\n\\nThe name of the link in", + "title": "Create (Beta) \u2014 DevRev | Docs" }, { - "id": "ART-2139_KNOWLEDGE_NODE-1", - "text": "https://api.devrev.ai/link-types.custom.create \\\\ |\\n| > | -H \"Authorization: Bearer \" \\\\ |\\n| > | -H \"Content-Type: application/json\" \\\\ |\\n| > | -d \\'{ |\\n| > | \"backward_name\": \"string\", |\\n| > | \"forward_name\": \"string\", |\\n| > | \"name\": \"string\", |\\n| > | \"source_types\": [ |\\n| > | {} |\\n| > | ], |\\n| > | \"target_types\": [ |\\n| > | {} |\\n| > | ] |\\n| > | }\\' |\\n```\\n\\n[Try it](/beta/api-reference/customization/custom-link-type-create?explorer=true)\\n\\n201Created\\n\\n```\\n| | |\\n|", - "title": "Create Link Types Custom | DevRev | Docs" + "id": "ART-1549_KNOWLEDGE_NODE-121", + "text": "object.\\n\\ntitle string Optional\\n\\nUpdates the title of the custom object.\\n\\nResponse.\\n\\nThis endpoint returns an object.\\ncustom_object object\\nShow 10 properties\\nAPI Reference customization Custom Link Type Create.\\n\\nPOST https://api.devrev.ai / link-types.custom.create\\n\\nCreates a custom link type.\\n\\nRequest.\\n\\nThis endpoint expects an object.\\nbackward_name string Required\\n\\nThe name of the link in the backward direction.\\n\\nforward_name string Required\\n\\nThe name of the link in", + "title": "List Post (Beta) \u2014 DevRev | Docs" } ] }, @@ -4316,54 +4316,54 @@ "query": "where can I view my articles in DevRev", "retrievals": [ { - "id": "ART-4065_KNOWLEDGE_NODE-4", - "text": "* [Blog](https://devrev.ai/blog)\\n * [Events](https://devrev.ai/events)\\n * [News](https://devrev.ai/blog?category=news)\\n * [Case Studies](https://devrev.ai/case-study)\\n * [Documentation](https://docs.devrev.ai/)\\n * [API Reference](https://docs.devrev.ai/api/)\\n * [The Book of DevRev](https://thebook.devrev.ai/)\\n * [Partner Program](https://devrev.ai/partners)\\n * [Startup Program](https://devrev.ai/startups)\\n\\nCompany\\n\\n * [About](https://devrev.ai/about)\\n *", - "title": "Delete Article \u2014 DevRev | Docs" + "id": "ART-15295_KNOWLEDGE_NODE-0", + "text": "b'List Articles | DevRev | Docs\\n\\n[![]()![]()](https://developer.devrev.ai/)\\n\\nPublic\\n\\nPublic\\n\\nSearch\\n\\n`/`\\n\\n[API Reference](/api-reference/getting-started)[articles](/api-reference/articles/create-article)\\n\\nList Articles\\n=============\\n\\nCopy page\\n\\nGET\\n\\nhttps://api.devrev.ai/articles.list\\n\\nGET\\n\\n/articles.list\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl https://api.devrev.ai/articles.list \\\\ |\\n| > | -H \"Authorization: Bearer \" |\\n```\\n\\n[Try", + "title": "List Articles | DevRev | Docs" }, { - "id": "ART-4064_KNOWLEDGE_NODE-19", - "text": "[Documentation](https://docs.devrev.ai/)\\n * [API Reference](https://docs.devrev.ai/api/)\\n * [The Book of DevRev](https://thebook.devrev.ai/)\\n * [Partner Program](https://devrev.ai/partners)\\n * [Startup Program](https://devrev.ai/startups)\\n\\nCompany\\n\\n * [About](https://devrev.ai/about)\\n * [People](https://devrev.ai/people)\\n * [Careers](https://devrev.ai/careers)\\n * [Places](https://devrev.ai/places)\\n * [Invest](https://revd.devrev.ai/)\\n * [What Why", - "title": "Create Article \u2014 DevRev | Docs" + "id": "ART-15726_KNOWLEDGE_NODE-0", + "text": "b\"If you just imported a bunch of articles from your favorite external system, but can't see them in DevRev, the most important question to ask yourself is whether that article was shared with you in the external system. Airdrop is permission-aware for articles, so if an article (or document, or page, whatever gets imported as an Airdrop article) was not shared with you in the external system, then you won't have access to it in DevRev (even if you're an admin), assuming the default visibility", + "title": "Visibility of Airdrop-imported articles" }, { - "id": "ART-4065_KNOWLEDGE_NODE-8", - "text": "Inc.\\n\\n[](https://devrev.ai)\\n\\n * Product\\n * Platform\\n * Solutions\\n * Marketplace\\n * Company\\n * Resources\\n * [Pricing](https://devrev.ai/pricing)\\n\\n __\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](https://devrev.ai/request-a-demo)\\n\\n[](https://devrev.ai)\\n\\n __\\n\\nProduct __\\n\\nPlatform __\\n\\nSolutions __\\n\\nMarketplace __\\n\\nCompany __\\n\\nResources __\\n\\n[Pricing](https://devrev.ai/pricing)\\n\\n[Login](https://app.devrev.ai/login)[Book a", - "title": "Delete Article \u2014 DevRev | Docs" + "id": "ART-1964_KNOWLEDGE_NODE-27", + "text": "the top of the DevRev app main page, and select either **Ticket** or **Issue**.\\n2. Click the template icon next to the **Select Subtype** drop-down menu and select a template. The selected template is applied to the object.\\n\\nUsing article templates\\n-----------------------\\n\\n1. Under [**Settings > Knowledge Base**](https://app.devrev.ai/devrev/settings/knowledge-base/articles), go to **View Templates**. A modal opens, showing a list and preview of the available templates.\\n2. Select a", + "title": "Templates | Computer by DevRev | DevRev" }, { - "id": "ART-4070_KNOWLEDGE_NODE-21", - "text": "__\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](https://devrev.ai/request-a-demo)\\n\\n[](https://devrev.ai)\\n\\n __\\n\\nProduct __\\n\\nPlatform __\\n\\nSolutions __\\n\\nMarketplace __\\n\\nCompany __\\n\\nResources __\\n\\n[Pricing](https://devrev.ai/pricing)\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](https://devrev.ai/request-a-demo)\\n\\n'", - "title": "Update Article \u2014 DevRev | Docs" + "id": "ART-4068_KNOWLEDGE_NODE-1", + "text": "__\\n\\n[Pricing](https://devrev.ai/pricing)\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](https://devrev.ai/request-a-demo)\\n\\n[API Reference](/public/api-reference/getting-started)[Articles](/public/api-reference/articles/create-article)\\n\\n# List Articles\\n\\nGET\\n\\nhttps://api.devrev.ai/articles.list\\n\\nTry it\\n\\nLists a collection of articles.\\n\\n### Query parameters\\n\\napplies_to_partslist of stringsOptional\\n\\nFilters for articles belonging to any of the provided", + "title": "List Articles \u2014 DevRev | Docs" }, { - "id": "ART-4065_KNOWLEDGE_NODE-5", - "text": "[People](https://devrev.ai/people)\\n * [Careers](https://devrev.ai/careers)\\n * [Places](https://devrev.ai/places)\\n * [Invest](https://revd.devrev.ai/)\\n * [What Why How](https://devrev.ai/what-why-how)\\n\\nConnect\\n\\n * [Contact ](mailto:humansofdevrev@devrev.ai)\\n * [Instagram ](https://www.instagram.com/devrev)\\n * [Medium ](https://medium.com/devrev)\\n * [Linkedin ](https://www.linkedin.com/company/devrev)\\n * [X (formerly Twitter)](https://twitter.com/devrev)\\n *", - "title": "Delete Article \u2014 DevRev | Docs" + "id": "ART-15726_KNOWLEDGE_NODE-2", + "text": "articles\\n\\nAs a last resort, you can ask the Airdrop team to check whether the articles are indeed in DevRev's database\"", + "title": "Visibility of Airdrop-imported articles" }, { - "id": "ART-1985_KNOWLEDGE_NODE-51", - "text": "Submitted for review\\n + *Ready to Publish*: All reviewers have approved\\n\\nArticle analytics\\n-----------------\\n\\nArticle analytics in DevRev provides a customized prebuilt dashboard to assess whether customers can find relevant articles to address their queries.\\n\\nAccess analytics under **Settings** > **Support** > **Article analytics**.\\n\\nThe dashboard shows the effectiveness of your knowledge base for both customers and internal employees with these metrics:\\n\\n* Viewership: Total", - "title": "Articles | Knowledge Base | Computer for Support Teams | DevRev" + "id": "ART-17230_KNOWLEDGE_NODE-12", + "text": "5 | |\\n| 6 | with the company email. |\\n| 7 |

|\\n```\\n\\nThe content in DevRev should look like this:\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 |

|\\n| 2 | You can create an account and log-in |\\n| 3 | |\\n| 4 | only |\\n| 5 | |\\n| 6 | with the company email. |\\n| 7 |

|\\n```\\n\\nWhere `don:core:dvrv-us-1:devo/0:article/10` is the DevRev article ID corresponding to external article", + "title": "Rich text fields | DevRev | Docs" }, { - "id": "ART-1985_KNOWLEDGE_NODE-24", - "text": "[Product demos](/docs/DevRevU/demos)\\n\\nOn this page\\n\\n* [Article management](#article-management)\\n* [Create an article](#create-an-article)\\n* [Edit article content and settings](#edit-article-content-and-settings)\\n* [Delete articles](#delete-articles)\\n* [Bulk change options](#bulk-change-options)\\n* [Status settings](#status-settings)\\n* [Visibility settings](#visibility-settings)\\n* [Article visibility](#article-visibility)\\n* [Storage limits for", - "title": "Articles | Knowledge Base | Computer for Support Teams | DevRev" + "id": "ART-4066_KNOWLEDGE_NODE-1", + "text": "__\\n\\n[Pricing](https://devrev.ai/pricing)\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](https://devrev.ai/request-a-demo)\\n\\n[API Reference](/public/api-reference/getting-started)[Articles](/public/api-reference/articles/create-article)\\n\\n# Get Article\\n\\nGET\\n\\nhttps://api.devrev.ai/articles.get\\n\\nTry it\\n\\nGets an article.\\n\\n### Query parameters\\n\\nidstringRequired`format: \"id\"`\\n\\nThe ID of the required article.\\n\\ndev_orgstringOptional`format: \"id\"`\\n\\nOptional Dev Org ID for the", + "title": "Get Article \u2014 DevRev | Docs" }, { - "id": "ART-4065_KNOWLEDGE_NODE-9", - "text": "demo](https://devrev.ai/request-a-demo)\\n\\n'", - "title": "Delete Article \u2014 DevRev | Docs" + "id": "ART-1985_KNOWLEDGE_NODE-37", + "text": "Storage limits for articles\\n\\n* There is no limit to the number of articles that can be created in the DevRev knowledge base.\\n* Each article is stored as an artifact, with a maximum size of 250 MB per artifact.\\n\\n### Enable customer access for your knowledge base\\n\\nTo make your help center, including your knowledge base, accessible to the public, go to **[Settings > Plug & Portal > Portal Settings](https://app.devrev.ai/?setting=portal-settings%2Fconfiguration)** and enable **Help Center**", + "title": "Articles | Knowledge Base | Computer for Support Teams | DevRev" }, { - "id": "ART-4066_KNOWLEDGE_NODE-0", - "text": "b'[](/public/api-reference/articles/get-article)\\n\\nPublic\\n\\n[](https://devrev.ai)\\n\\n * Product\\n * Platform\\n * Solutions\\n * Marketplace\\n * Company\\n * Resources\\n * [Pricing](https://devrev.ai/pricing)\\n\\n __\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](https://devrev.ai/request-a-demo)\\n\\n[](https://devrev.ai)\\n\\n __\\n\\nProduct __\\n\\nPlatform __\\n\\nSolutions __\\n\\nMarketplace __\\n\\nCompany __\\n\\nResources", - "title": "Get Article \u2014 DevRev | Docs" + "id": "ART-1985_KNOWLEDGE_NODE-49", + "text": "click the **Create** drop-down.\\n2. Select **Create and submit for review**.\\n3. Add reviewers to the approval process, who receive notifications and are tagged in the **Discussions** tab.\\n\\nArticle approval is available only for articles created natively within DevRev.\\n\\n### Review an article\\n\\n1. Open the article and locate the **Review** icon at the top right.\\n2. Choose to either **Request Changes** or **Approve**.\\n3. If requesting changes, provide feedback in the placeholder.\\n\\nAn", + "title": "Articles | Knowledge Base | Computer for Support Teams | DevRev" }, { - "id": "ART-4068_KNOWLEDGE_NODE-19", - "text": "[About](https://devrev.ai/about)\\n * [People](https://devrev.ai/people)\\n * [Careers](https://devrev.ai/careers)\\n * [Places](https://devrev.ai/places)\\n * [Invest](https://revd.devrev.ai/)\\n * [What Why How](https://devrev.ai/what-why-how)\\n\\nConnect\\n\\n * [Contact ](mailto:humansofdevrev@devrev.ai)\\n * [Instagram ](https://www.instagram.com/devrev)\\n * [Medium ](https://medium.com/devrev)\\n * [Linkedin ](https://www.linkedin.com/company/devrev)\\n * [X (formerly", - "title": "List Articles \u2014 DevRev | Docs" + "id": "ART-4218_KNOWLEDGE_NODE-30", + "text": "a one-time sync to DevRev, follow these steps:\\n\\n1. Go to **Settings** > **Integrations** > **AirSyncs**.\\n2. Locate the previously imported project.\\n3. Select the **\\xe2\\x8b\\xae** > **Sync Azure DevOps Wikis to DevRev** option.\\n\\n![]()\\n\\nA one-time sync may overwrite fields in previously imported articles, even if they were modified in DevRev.\\n\\n### Historical AirSyncs\\n\\nTo view currently running and previous AirSyncs from various sources, do the following:\\n\\n1. Go to **Settings** >", + "title": "Azure DevOps Wikis AirSync | AirSync | Snap-ins | DevRev" } ] }, @@ -4372,54 +4372,54 @@ "query": "Next Best Action recommendations based on case context and history", "retrievals": [ { - "id": "ART-2133_KNOWLEDGE_NODE-56", - "text": "now.\\n\\n\\n\\nTime Travel (Context | Hisory) Hyper-Personalized Ontology | Fine-Tuning Predictive vs. Proactive Beyond SLAs Gustomer-Centric Lowest Latency Notifications Mobile-First User-over-Buyer Grassrocts Community | Word-of-Mouth Design-First | Consumer- Grade\\n\\n\\n\\nDeep Work | LLIs before Channels Cravi-n-index Everything Enterprise Shortcuts Discern Real Time Iterventions No Human-inthe-Loop Defloct L Deduplicate Text2SQL | Text2Visualization | TextdManagers Toxt2Logacy Voice for", - "title": "The Essential Methodology: Less but Better" + "id": "ART-1272_KNOWLEDGE_NODE-3", + "text": "actions enriched by context.\\n\\nSnap-in\\n-------\\n\\nSnap-ins are collections of objects that extend DevRev\\xe2\\x80\\x99s core platform value. These objects include automation, event sources, keyrings, custom types, and vistas. With snap-ins, developers can develop at \\xe2\\x80\\x9carms-length\\xe2\\x80\\x9d and without making any changes to DevRev\\xe2\\x80\\x99s core platform.\\n\\nSnap-in developers interact with DevRev objects through APIs, get updates on DevRev objects through webhooks, and register", + "title": "Concepts | DevRev | Docs" }, { - "id": "ART-2133_KNOWLEDGE_NODE-22", - "text": "suboptimal decisions. Only by going back in time can best decisions be taken.\\n\\n\\n\\nFine Tuning Customer ontologies \\xe2\\x80\\x93 {product, process, organization, skills} taxonomy, and people identities \\xe2\\x80\\x93 are extremely important in this day and age of AI to make models accurate and relevant within an enterprise. The Essential methodology embraces model \\xef\\xac\\x81ne-tuning as a necessary tenet of hyper-personalization.\\n\\nPredictive Servicing A large proportion of businesses are", - "title": "The Essential Methodology: Less but Better" + "id": "ART-12390_KNOWLEDGE_NODE-0", + "text": "b'Workflow action library | Workflows | Computer by DevRev | DevRev\\n\\n* Computer\\n* Resources\\n* [Our Customers](/case-study)\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](/request-a-demo)\\n\\nComputer\\n\\nResources\\n\\n[Our Customers](/case-study)\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](/request-a-demo)\\n\\nSearch\\n\\n`CTRL`\\xc2\\xa0+\\xc2\\xa0`K`\\n\\n* [Introduction](/docs)\\n* [Computer by DevRev](/docs/intro)\\n\\n + [Core concepts](/docs/product/core)\\n +", + "title": "Workflow action library | Workflows | Computer by DevRev | DevRev" }, { - "id": "ART-13178_KNOWLEDGE_NODE-44", - "text": "action demonstrates this approach.\\n * **Goal-based agents** evaluate actions based on how they contribute to achieving specific objectives. DevRev\\xe2\\x80\\x99s product development AI agents exemplify this approach by coordinating activities specifically designed to meet release deadlines and quality targets.\\n * **Utility-based agents** use sophisticated evaluation mechanisms to maximize overall benefit across multiple objectives. For instance, a marketing campaign optimizer might balance", - "title": "Understanding Agentic AI: Capabilities and Implications for the Future" + "id": "ART-1290_KNOWLEDGE_NODE-26", + "text": "\"action_id\": \"example_other\", |\\n| 61 | \"type\": \"plain_text_input\" |\\n| 62 | }, |\\n| 63 | \"label\": { |\\n| 64 | \"text\": \"Additional notes\", |\\n| 65 | \"type\": \"plain_text\" |\\n| 66 | }, |\\n| 67 | \"optional\": true, |\\n| 68 | \"type\": \"input_layout\" |\\n| 69 | } |\\n| 70 | ], |\\n| 71 | \"submit_action\": { |\\n| 72 | \"action_id\": \"example_button\", |\\n| 73 | \"style\": \"primary\", |\\n| 74 | \"text\": { |\\n| 75 | \"text\": \"Submit\", |\\n| 76 | \"type\": \"plain_text\" |\\n| 77 | }, |\\n| 78 | \"type\": \"button\", |\\n| 79 |", + "title": "Snapkit | DevRev | Docs" }, { - "id": "ART-15621_KNOWLEDGE_NODE-17", - "text": "activity patterns for context-aware results\"\\n\\nBattle Tactic : Demonstrate comprehensive data access in head-to-head comparisons\\n\\n2. Conversational Analytics & Workflows\\n\\nPositioning : \"DevRev\\'s Search Agent combines search with deep object relationships, delivering conversational analytics and RCA through natural conversations while proactively surfacing business-critical patterns\"\\n\\nBattle Tactic : Show workflow automation and analytics capabilities that Glean cannot deliver\\n\\n3.", - "title": "Glean - Competitive - for the PLuG on website" + "id": "ART-1290_KNOWLEDGE_NODE-59", + "text": "|\\n| 1 | { |\\n| 2 | \"element\": { |\\n| 3 | \"action_id\": \"age\", |\\n| 4 | \"max_value\": 120, |\\n| 5 | \"min_value\": 10, |\\n| 6 | \"type\": \"number_input\" |\\n| 7 | }, |\\n| 8 | \"label\": { |\\n| 9 | \"text\": \"Age\", |\\n| 10 | \"type\": \"plain_text\" |\\n| 11 | }, |\\n| 12 | \"type\": \"input_layout\" |\\n| 13 | } |\\n```\\n\\n*Action payload*\\n\\nInherits `type`, `action_id`, `action_type`, and `timestamp` from [Base payload](/snapin-development/references/snapkit#base-payload), `type` is set to", + "title": "Snapkit | DevRev | Docs" }, { - "id": "ART-13178_KNOWLEDGE_NODE-43", - "text": "business scenarios:\\n\\n * **Simple reflex agents** operate on straightforward condition-action rules without considering past experiences. For example, a basic customer inquiry routing system that assigns tickets based on predefined keywords falls into this category.\\n * **Model-based reflex agents** incorporate an internal model of the world, tracking the environment\\xe2\\x80\\x99s current state. A sales automation tool that considers past customer interactions when determining the next best", - "title": "Understanding Agentic AI: Capabilities and Implications for the Future" + "id": "ART-2814_KNOWLEDGE_NODE-5", + "text": "13| surface: issue \\n 14| snap_kit_action_name: show_test_cases \\n 15| initializer: upgrade_test_function_1 \\n 16| snap_kit_body: \\n 17| { \\n 18| \"snaps\":[] \\n 19| }\\n[/code] \\n \\n## Format of context passed to snap-kit action\\n\\n[code]\\n\\n 1| // The payload contains details and values of the snap-kit from which the action was invoked. \\n ---|--- \\n 2| interface Payload { \\n 3| action: { \\n 4| block_id:", + "title": "Snap Components \u2014 DevRev | Docs" }, { - "id": "ART-1954_KNOWLEDGE_NODE-35", - "text": "determined by the type of action, rather than solely by the actor performing the action.\\n\\nExamples:\\n\\n* If mentions are set to **Important** and a bot's notifications are set to **Others**, then bot mentions will only appear in the **Others** tab.\\n* If mentions are set to **Important** and a bot's notifications are also set to **Important**, then bot mentions will appear in the **Important** tab.\\n* If mentions are set to **Others** and a bot's notifications are set to **Important**, then", - "title": "Updates | Computer by DevRev | DevRev" + "id": "ART-1303_KNOWLEDGE_NODE-169", + "text": "customers impacted due to the incident.\\nmitigated_date datetime Optional\\nTimestamp when the incident was mitigated.\\nowned_by list of strings Optional\\nUser IDs of the users that own the incident.\\npia list of strings Optional\\nThe article ids of the Post-Incident Analysis(PIA) of the incident.\\nplaybooks list of strings Optional\\nThe article ids of the playbook(s) associated with the incident.\\nrelated_docs list of strings Optional\\nThe article ids of other documents associated with the", + "title": "Export Post \u2014 DevRev | Docs" }, { - "id": "ART-1989_KNOWLEDGE_NODE-37", - "text": "follow a common structure for easy categorization and search. If you have common themes or categories, the exact convention is up to you to standardize for your teams.\\n\\n One possible convention is Category-Subcategory-Specific command subject. For example:\\n\\n + Rerouting-Reroute to payments-Refund\\n + Rerouting-Reroute to payments-Payment failure\\n + Rerouting-Reroute to Sales\\n\\n[PreviousBest practices for documentation that supports AI](/docs/product/writing-bp)[NextService-level", - "title": "Commands | Computer for Support Teams | DevRev" + "id": "ART-1607_KNOWLEDGE_NODE-164", + "text": "customers impacted due to the incident.\\nmitigated_date datetime Optional\\nTimestamp when the incident was mitigated.\\nowned_by list of strings Optional\\nUser IDs of the users that own the incident.\\npia list of strings Optional\\nThe article ids of the Post-Incident Analysis(PIA) of the incident.\\nplaybooks list of strings Optional\\nThe article ids of the playbook(s) associated with the incident.\\nrelated_docs list of strings Optional\\nThe article ids of other documents associated with the", + "title": "Get Post \u2014 DevRev | Docs" }, { - "id": "ART-1995_KNOWLEDGE_NODE-30", - "text": "a continuous planning approach that allows you to prioritize work in a more intuitive way.\\n\\n When creating an issue, you can categorize it under the following buckets:\\n\\n + **Now:** What is currently being executed.\\n + **Next:** Estimate of what will be worked on within a specific timeframe.\\n + **Backlog/Later:** Prioritized issues expected to be committed to in a later timeframe.\\n + **Triage:** Triage is a process to prioritize work items (issues or tickets) based on severity, risk,", - "title": "Build best practices | Computer for Builders | DevRev" + "id": "ART-1305_KNOWLEDGE_NODE-171", + "text": "customers impacted due to the incident.\\nmitigated_date datetime Optional\\nTimestamp when the incident was mitigated.\\nowned_by list of strings Optional\\nUser IDs of the users that own the incident.\\npia list of strings Optional\\nThe article ids of the Post-Incident Analysis(PIA) of the incident.\\nplaybooks list of strings Optional\\nThe article ids of the playbook(s) associated with the incident.\\nrelated_docs list of strings Optional\\nThe article ids of other documents associated with the", + "title": "Get Post \u2014 DevRev | Docs" }, { - "id": "ART-1990_KNOWLEDGE_NODE-26", - "text": "worked on. This approach directly enables developers to pick up work that drives customer and business impact on a continuous basis. The power of continuous planning comes through deconstructing complex processes in favor of more intuitive and integrated workflows.\\n\\n\\xf0\\x9f\\x8e\\xa5 Video: Prioritize backlog by customer impact\\n\\nPrioritized work\\n----------------\\n\\nInstead of antiquated concepts requiring domain knowledge, prioritized work is defined by a state machine into *Now*, *Next*,", - "title": "Now, Next, Later | Computer for Builders | DevRev" + "id": "ART-1822_KNOWLEDGE_NODE-164", + "text": "customers impacted due to the incident.\\nmitigated_date datetime Optional\\nTimestamp when the incident was mitigated.\\nowned_by list of strings Optional\\nUser IDs of the users that own the incident.\\npia list of strings Optional\\nThe article ids of the Post-Incident Analysis(PIA) of the incident.\\nplaybooks list of strings Optional\\nThe article ids of the playbook(s) associated with the incident.\\nrelated_docs list of strings Optional\\nThe article ids of other documents associated with the", + "title": "Create \u2014 DevRev | Docs" }, { - "id": "ART-12390_KNOWLEDGE_NODE-6", - "text": "+ [Turing AI agent](/docs/product/conversational-bot)\\n\\n - [Best practices for documentation that supports AI](/docs/product/writing-bp)\\n + [Commands](/docs/product/commands)\\n + [Service-level agreement](/docs/product/sla)\\n + [Operational-level agreement](/docs/product/ola)\\n + [Support snap-ins](/docs/product/snapins-support)\\n* [Computer for Builders](/docs/product/build)\\n\\n + [Issues](/docs/product/issues)\\n + [Now, Next, Later](/docs/product/nnl)\\n + [Sprint", - "title": "Workflow action library | Workflows | Computer by DevRev | DevRev" + "id": "ART-1826_KNOWLEDGE_NODE-164", + "text": "customers impacted due to the incident.\\nmitigated_date datetime Optional\\nTimestamp when the incident was mitigated.\\nowned_by list of strings Optional\\nUser IDs of the users that own the incident.\\npia list of strings Optional\\nThe article ids of the Post-Incident Analysis(PIA) of the incident.\\nplaybooks list of strings Optional\\nThe article ids of the playbook(s) associated with the incident.\\nrelated_docs list of strings Optional\\nThe article ids of other documents associated with the", + "title": "Get Post \u2014 DevRev | Docs" } ] }, @@ -4428,53 +4428,53 @@ "query": "Pro license pricing cost subscription plan", "retrievals": [ { - "id": "ART-962_KNOWLEDGE_NODE-0", - "text": "b'1. Core Pricing Plans:\\n\\nStarter: Ideal for small teams (up to 15 users) navigating product-market fit.\\n\\nLimited Time Offer: $1,000 credits.\\n\\nPlatform License: $9.99 per monthly active user (MAU).\\n\\nSupport License: $9.99 per MAU.\\n\\nFeatures:\\n\\nUnlimited viewers at no extra charge.\\n\\nConverge Issue and Ticket Management.\\n\\nMap your product features with Parts and Trails\\n\\nCustomize your data and insights with Vistas.\\n\\nCustomer and user management.\\n\\nLive chat and deflection", + "id": "ART-962_KNOWLEDGE_NODE-2", + "text": "offer).\\n\\n24/5 customer support.\\n\\nPricing: Platform license at $24.99 per MAU, support license at $34.99 per MAU.\\n\\nUltimate: Tailored for complex organizations with strict requirements.\\n\\nAll features from Pro, plus:\\n\\nAudit logging.\\n\\nEnhanced storage and retention.\\n\\nSLA-driven support response times.\\n\\nAdvanced object, subtype, and attribute customization.\\n\\nMulti-region high availability.\\n\\nLive read replica sandboxes.\\n\\nCustom pricing based on specific needs.\\n\\n2.", "title": "DevRev Pricing" }, { - "id": "ART-962_KNOWLEDGE_NODE-2", - "text": "offer).\\n\\n24/5 customer support.\\n\\nPricing: Platform license at $24.99 per MAU, support license at $34.99 per MAU.\\n\\nUltimate: Tailored for complex organizations with strict requirements.\\n\\nAll features from Pro, plus:\\n\\nAudit logging.\\n\\nEnhanced storage and retention.\\n\\nSLA-driven support response times.\\n\\nAdvanced object, subtype, and attribute customization.\\n\\nMulti-region high availability.\\n\\nLive read replica sandboxes.\\n\\nCustom pricing based on specific needs.\\n\\n2.", + "id": "ART-962_KNOWLEDGE_NODE-0", + "text": "b'1. Core Pricing Plans:\\n\\nStarter: Ideal for small teams (up to 15 users) navigating product-market fit.\\n\\nLimited Time Offer: $1,000 credits.\\n\\nPlatform License: $9.99 per monthly active user (MAU).\\n\\nSupport License: $9.99 per MAU.\\n\\nFeatures:\\n\\nUnlimited viewers at no extra charge.\\n\\nConverge Issue and Ticket Management.\\n\\nMap your product features with Parts and Trails\\n\\nCustomize your data and insights with Vistas.\\n\\nCustomer and user management.\\n\\nLive chat and deflection", "title": "DevRev Pricing" }, { - "id": "ART-15627_KNOWLEDGE_NODE-1", - "text": "Starter, Pro, and Ultimate. This ensures flexibility and scalability as your business needs evolve. Most plans are priced per user per month, while PLuG offers usage-based pricing options. Is there a free trial available? Yes, DevRev offers a\\xc2\\xa0 45-day free trial \\xc2\\xa0for both Build and Support paid plans (Starter and Pro tiers). What are my payment options? You can use your credit card to pay for any plan. If you sign up for a Pro Plan, DevRev can invoice you annually and offer a", + "id": "ART-15627_KNOWLEDGE_NODE-5", + "text": "included in Build Pro ($24.99/month)?\\n\\nEverything in Starter\\n\\nCustomizable issue management\\n\\nAdvanced reporting & analytics\\n\\n45-day free trial\\n\\nWhat\\'s included in Build Ultimate?\\n\\nEverything in Pro\\n\\nFull object model customization and unlimited integrations\\n\\nEnterprise-grade security, compliance, controls, and policies\\n\\nDevRev PLuG Pricing For detailed pricing and to get started: \\xc2\\xa0 https://devrev.ai/pricing/plug What are the PLuG pricing options?\\n\\nFree : AI-powered", "title": "DevRev Pricing - for the PLuG on the website" }, { - "id": "ART-15627_KNOWLEDGE_NODE-13", - "text": "tier or contact sales for custom arrangements. Is there an enterprise discount for annual payments? Yes, for Pro Plans and above, DevRev can invoice annually and offers discounts. Contact\\xc2\\xa0 support@devrev.ai \\xc2\\xa0to discuss annual pricing options.'", - "title": "DevRev Pricing - for the PLuG on the website" + "id": "ART-3908_KNOWLEDGE_NODE-5", + "text": "users per product. While the $10K credits typically cover around 14 pro-level licenses based on current pricing, you\\xe2\\x80\\x99re free to use as many licenses based on your business needs. Q:-How do my credits get consumed throughout the year?\\n\\nA:- Credits are consumed monthly, primarily based on the number of licenses you provision and any custom integrations you request for. To make the most of your credits, we recommend starting with just the minimum number of licenses you need and", + "title": "DevRev for Startups" }, { - "id": "ART-962_KNOWLEDGE_NODE-3", - "text": "Usage-Based Costs:\\n\\nOn top of the core plans, DevRev charges for specific usage:\\n\\nUser and Customer Management: $0.20 per user, per month.\\n\\nConversations:\\n\\n$0.01 per anonymous user conversation, per month.\\n\\n$0.45 per verified user conversation, per month.\\n\\nStorage:\\n\\n$2.00 per extra GB of file storage, per month.\\n\\n$25.00 per extra GB of base storage, per month.\\n\\n3. Additional Considerations:\\n\\nAuthorization roles and profiles: $10.00 per MAU (optional add-on).\\n\\nFree tier:", - "title": "DevRev Pricing" + "id": "ART-15258_KNOWLEDGE_NODE-5", + "text": "users per product. While the $10K credits typically cover around 14 pro-level licenses based on current pricing, you\\xe2\\x80\\x99re free to use as many licenses based on your business needs. Q:-How do my credits get consumed throughout the year?\\n\\nA:- Credits are consumed monthly, primarily based on the number of licenses you provision and any custom integrations you request for. To make the most of your credits, we recommend starting with just the minimum number of licenses you need and", + "title": "DevRev - Website - FAQs" }, { - "id": "ART-15627_KNOWLEDGE_NODE-3", - "text": "migration and integrations\\n\\nReady-to-go reporting and analytics\\n\\n45-day free trial\\n\\nWhat\\'s included in Support Pro ($59.99/month)?\\n\\nEverything in Starter\\n\\nAdvanced reporting & analytics\\n\\nCustom SLA and routing policies\\n\\nCustomizable object and data types\\n\\n45-day free trial\\n\\nWhat\\'s included in Support Ultimate?\\n\\nEverything in Pro\\n\\nFull object model customization and unlimited integrations\\n\\nEnterprise-grade security, compliance, controls, and policies\\n\\nCustom pricing", + "id": "ART-15627_KNOWLEDGE_NODE-1", + "text": "Starter, Pro, and Ultimate. This ensures flexibility and scalability as your business needs evolve. Most plans are priced per user per month, while PLuG offers usage-based pricing options. Is there a free trial available? Yes, DevRev offers a\\xc2\\xa0 45-day free trial \\xc2\\xa0for both Build and Support paid plans (Starter and Pro tiers). What are my payment options? You can use your credit card to pay for any plan. If you sign up for a Pro Plan, DevRev can invoice you annually and offer a", "title": "DevRev Pricing - for the PLuG on the website" }, { - "id": "ART-15627_KNOWLEDGE_NODE-5", - "text": "included in Build Pro ($24.99/month)?\\n\\nEverything in Starter\\n\\nCustomizable issue management\\n\\nAdvanced reporting & analytics\\n\\n45-day free trial\\n\\nWhat\\'s included in Build Ultimate?\\n\\nEverything in Pro\\n\\nFull object model customization and unlimited integrations\\n\\nEnterprise-grade security, compliance, controls, and policies\\n\\nDevRev PLuG Pricing For detailed pricing and to get started: \\xc2\\xa0 https://devrev.ai/pricing/plug What are the PLuG pricing options?\\n\\nFree : AI-powered", - "title": "DevRev Pricing - for the PLuG on the website" + "id": "ART-4169_KNOWLEDGE_NODE-2", + "text": "Credits\\n---------------------------------\\n\\nAvail Pro-level access: Get $6K in credits at sign-up, plus $4K by completing key onboarding milestones\\n-------------------------------------------------------------------------------------------------------\\n\\n50% Off on Follow-up Commit\\n---------------------------\\n\\nClaim discount on the follow-on one-year commitment within 6 months of credits", + "title": "DevRev For Startups" }, { - "id": "ART-15627_KNOWLEDGE_NODE-9", - "text": "that time, DevRev starts charging your credit card for subscription and consumption costs. What is a Platform vs. Support User?\\n\\nPlatform users : Have full access to the Build App and gain visibility across an organization to understand the context between product and customer\\n\\nSupport Users : Users that create or update customer-related records. The per-seat pricing is in addition to the platform license cost and includes customer records (RevO or RevU), plus other related records like", - "title": "DevRev Pricing - for the PLuG on the website" + "id": "ART-962_KNOWLEDGE_NODE-4", + "text": "Limited functionality for individual users and small teams.\\n\\n4. Summary:\\n\\nDevRev offers flexible pricing to cater to diverse needs.\\n\\nSmall teams can start with the Starter plan and scale up as needed.\\n\\nLarger organizations may benefit from Pro or Ultimate plans.\\n\\nUsage-based costs add transparency and control over spending.\\n\\nCarefully assess your team size, usage patterns, and desired features before choosing a plan.'", + "title": "DevRev Pricing" }, { - "id": "ART-15627_KNOWLEDGE_NODE-2", - "text": "discount. Contact\\xc2\\xa0 support@devrev.ai \\xc2\\xa0to discuss annual pricing. DevRev Support Pricing For detailed pricing and to get started: \\xc2\\xa0 https://devrev.ai/pricing/support What are the Support pricing plans?\\n\\nStarter : $19.99 per user/month (up to 10 users)\\n\\nPro : $59.99 per user/month\\n\\nUltimate : Custom pricing (contact sales)\\n\\nWhat\\'s included in Support Starter ($19.99/month)?\\n\\nAI agents, assistants, and deflection\\n\\nModern omnichannel ticketing platform\\n\\nData", + "id": "ART-15627_KNOWLEDGE_NODE-9", + "text": "that time, DevRev starts charging your credit card for subscription and consumption costs. What is a Platform vs. Support User?\\n\\nPlatform users : Have full access to the Build App and gain visibility across an organization to understand the context between product and customer\\n\\nSupport Users : Users that create or update customer-related records. The per-seat pricing is in addition to the platform license cost and includes customer records (RevO or RevU), plus other related records like", "title": "DevRev Pricing - for the PLuG on the website" }, { - "id": "ART-15627_KNOWLEDGE_NODE-7", - "text": "session record)\\n\\nWhat\\'s included in PLuG Ultimate?\\n\\nAll Pay-as-you-go features\\n\\nAdvanced functionality for scale\\n\\nVolume discounting\\n\\nUnderstanding users wherever they are\\n\\nDevRev AgentOS Pricing For detailed pricing and to get started: \\xc2\\xa0 https://devrev.ai/pricing/agentos How is AgentOS priced? AgentOS is available only through custom pricing. Contact sales for a quote. What\\'s included in AgentOS?\\n\\nFlexible pricing models: usage-based or predictable fixed pricing\\n\\nFull", + "id": "ART-15627_KNOWLEDGE_NODE-13", + "text": "tier or contact sales for custom arrangements. Is there an enterprise discount for annual payments? Yes, for Pro Plans and above, DevRev can invoice annually and offers discounts. Contact\\xc2\\xa0 support@devrev.ai \\xc2\\xa0to discuss annual pricing options.'", "title": "DevRev Pricing - for the PLuG on the website" } ] @@ -4484,24 +4484,19 @@ "query": "count tickets with customer CSAT review", "retrievals": [ { - "id": "ART-2011_KNOWLEDGE_NODE-26", - "text": "**CSAT on ticket** > **Configure**.\\n2. Select the channel you want to send the survey on in **Survey channel**.\\n3. Write introductory text for the survey in **Survey introductory text**.\\n\\n ![]()\\n\\n To include the customer's name in the CSAT survey emails, add a key {{customer\\\\_name}} to the introductory text configuration of the CSAT.\\n4. Customize your survey response scale which is shown to the customers to select from in **Survey response scale**.\\n5. To collect additional feedback", - "title": "CSAT on ticket | Automate | Snap-ins | DevRev" - }, - { - "id": "ART-2011_KNOWLEDGE_NODE-24", - "text": "[Snap-ins](/docs/snapins)\\n[Automate](/docs/automate)\\n[CSAT on ticket](/docs/automations/csat-tickets)\\n\\nCSAT on ticket\\n==============\\n\\n[CSAT on ticket](/marketplace/csat_on_ticket_dwx7b2bp) offers a simplified approach to measure customer satisfaction level for the ticket resolved with the help of surveys which can be utilized to enhance the overall customer experience.\\n\\nThis snap-in displays a customer satisfaction survey to customers after their ticket gets resolved. The questions can", - "title": "CSAT on ticket | Automate | Snap-ins | DevRev" + "id": "ART-1003_KNOWLEDGE_NODE-20", + "text": "AverageResolutionTime\\nFROM tickets t\\nWHERE t.status = 'resolved'\\nAND EXTRACT(@period FROM t.created_at) = EXTRACT(@period FROM CURRENT_DATE);\\n-- NOTE: Replace @period with 'DAY', 'WEEK', 'MONTH', or 'QUARTER'.\\n\\n\\nCustomer Satisfaction Score (CSAT)\\n\\n\\n Definition\\n \\n A metric that gauges customer satisfaction with the support provided, typically collected through surveys.\\n \\n \\n Calculation\\n \\n (Number of satisfied responses) / (Total number of responses) * 100\\n", + "title": "Understanding a Support Lead's Pain Points and KPIs" }, { - "id": "ART-2011_KNOWLEDGE_NODE-27", - "text": "from the customer along with the scale rating, ensure that the toggle for **Additional Feedback Request** configuration is enabled.\\n6. Write a query for the customers after the survey is populated in **Survey query**.\\n7. Write a message for the customers after the survey response is submitted in **Survey response message**.\\n8. Specify the time for the survey to expire (in minutes) in **Survey expires after**.\\n\\n ![]()\\n9. If you want to send the survey only once, enable the **Send survey", - "title": "CSAT on ticket | Automate | Snap-ins | DevRev" + "id": "ART-1004_KNOWLEDGE_NODE-9", + "text": "tickets\\nWHERE EXTRACT(@period FROM created_at) = EXTRACT(@period FROM CURRENT_DATE)\\nGROUP BY engineer_id;\\n-- NOTE: Replace @period with 'DAY', 'WEEK', 'MONTH', or 'QUARTER'.\\n\\n\\nIndividual Customer Satisfaction (CSAT) Score\\n\\n\\n Definition\\n \\n A metric that gauges customer satisfaction with the support provided by a specific engineer, typically collected through surveys.\\n \\n \\n Calculation\\n \\n (Number of satisfied responses for the engineer) / (Total number of", + "title": "Understanding a Support Engineer's Pain Points and KPIs" }, { - "id": "ART-2013_KNOWLEDGE_NODE-27", - "text": "customer's name in the CSAT survey emails, add a key {{customer\\\\_name}} to the introductory text configuration of the CSAT.\\n4. Customize your survey response scale which is shown to the customers to select from in **Survey response scale**.\\n5. To collect additional feedback from the customer along with the scale rating, ensure that the toggle for **Additional Feedback Request** configuration is enabled.\\n6. Write a query for the customers after the survey is populated in **Survey", - "title": "CSAT on conversation | Automate | Snap-ins | DevRev" + "id": "ART-1977_KNOWLEDGE_NODE-25", + "text": "Average CSAT rating for ticket Owners.\\n* **SLA breaches by Customer tier**\\n\\n Number of Tickets with SLA breaches for ticket owners.\\n* **Active Tickets**\\n\\n A distribution of tickets in Open and In Progress states and the respective owners.\\n* **Closed Tickets**\\n\\n A distribution of tickets in Closed state and the respective owners.\\n* **SLA breaches**\\n\\n Number of Tickets with SLA breaches for ticket owners.\\n* **Tickets Escalated**\\n\\n Number of tickets that are escalated by", + "title": "Ticket-Team Performance | Support analytics | Computer for Support Teams | DevRev" }, { "id": "ART-2011_KNOWLEDGE_NODE-25", @@ -4509,29 +4504,34 @@ "title": "CSAT on ticket | Automate | Snap-ins | DevRev" }, { - "id": "ART-2011_KNOWLEDGE_NODE-28", - "text": "only once per ticket** toggle.\\n10. If you want to automatically send CSAT surveys when tickets reach the *Resolved* stage, keep the **Trigger the CSAT survey based on configured rules** toggle turned off.\\n11. If you want to send CSAT at a specific ticket stage, turn the **Trigger the CSAT survey based on configured rules** toggle on and set up a custom workflow with the following configuration:\\n\\n| **Component** | **Details** |\\n| --- | --- |\\n| Trigger | Update Ticket |\\n| Stage Control |", + "id": "ART-1003_KNOWLEDGE_NODE-25", + "text": "* 100\\n \\n \\n\\n\\nSELECT (COUNT(*) * 100) / (SELECT COUNT(*) FROM tickets WHERE EXTRACT(@period FROM created_at) = EXTRACT(@period FROM CURRENT_DATE)) AS EscalationRate\\nFROM tickets\\nWHERE is_escalated = 1\\nAND EXTRACT(@period FROM created_at) = EXTRACT(@period FROM CURRENT_DATE);\\n-- NOTE: Replace @period with 'DAY', 'WEEK', 'MONTH', or 'QUARTER'.\\n\\n\\nAgent Utilization Rate\\n\\n\\n Definition\\n \\n The percentage of an engineer\\xe2\\x80\\x99s working hours spent on handling customer", + "title": "Understanding a Support Lead's Pain Points and KPIs" + }, + { + "id": "ART-2011_KNOWLEDGE_NODE-26", + "text": "**CSAT on ticket** > **Configure**.\\n2. Select the channel you want to send the survey on in **Survey channel**.\\n3. Write introductory text for the survey in **Survey introductory text**.\\n\\n ![]()\\n\\n To include the customer's name in the CSAT survey emails, add a key {{customer\\\\_name}} to the introductory text configuration of the CSAT.\\n4. Customize your survey response scale which is shown to the customers to select from in **Survey response scale**.\\n5. To collect additional feedback", "title": "CSAT on ticket | Automate | Snap-ins | DevRev" }, { - "id": "ART-2011_KNOWLEDGE_NODE-29", - "text": "If Else |\\n| Condition | When: Ticket Updated / Output > Stage > Name (Make sure that the stage name is in snake case.) |\\n| Action | Update Ticket |\\n| ID | Ticket Updated > Output > Id |\\n| List of Integrations | CSAT |\\n| Integrations | App CSAT Send Survey > Yes |\\n\\n1. Click **Save** > **Next** and deploy the snap-in.\\n\\n[PreviousCSAT on conversation](/docs/automations/csat-conv)[NextCSV work item uploader](/docs/automations/csv-work-item-uploader)\\n\\n#### On this page\\n\\n*", - "title": "CSAT on ticket | Automate | Snap-ins | DevRev" + "id": "ART-997_KNOWLEDGE_NODE-16", + "text": "\"type\": \"CSAT\",\\n // these can be kept disjoint and resolved\\n \"response\":\"good\",\\n ...\\n },\\n {\\n \"type\": \"feedback\",\\n \"response\":\"foobar\",\\n ...\\n }\\n ...\\n\\n\\nDon\\xe2\\x80\\x99t\\n\\n ...\\n \"id\":\"don:...:ticket/44\",\\n \"object_type\": \"ticket\",\\n \"csat_respose\": \"good\"\\n ...\\n\\n\\nAs new survey types come, nothing needs to be restructured and we have uniformity. Instead, we turn something from a early binding build-time item into something that can", + "title": "How to Write an Object Model That Doesn't Suck" }, { - "id": "ART-2011_KNOWLEDGE_NODE-5", - "text": "ticket conversion](/docs/product/conversation-ticket)\\n + [Tickets](/docs/product/tickets)\\n + [Routing](/docs/product/routing)\\n + [Support best practices](/docs/product/support-bp)\\n + [Customer portal](/docs/product/support-portal)\\n + [Questions & answers](/docs/product/qa)\\n + [Knowledge Base](/docs/product/knowledge-base)\\n\\n - [Articles](/docs/product/articles)\\n - [Collections](/docs/product/collection)\\n + [Turing AI agent](/docs/product/conversational-bot)\\n\\n - [Best", + "id": "ART-2011_KNOWLEDGE_NODE-0", + "text": "b\"CSAT on ticket | Automate | Snap-ins | DevRev\\n\\n* Computer\\n* Resources\\n* [Our Customers](/case-study)\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](/request-a-demo)\\n\\nComputer\\n\\nResources\\n\\n[Our Customers](/case-study)\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](/request-a-demo)\\n\\nSearch\\n\\n`CMD`\\xc2\\xa0+\\xc2\\xa0`K`\\n\\n* [Introduction](/docs)\\n* [Computer by DevRev](/docs/intro)\\n\\n + [Core concepts](/docs/product/core)\\n + [Apps](/docs/product/apps)\\n +", "title": "CSAT on ticket | Automate | Snap-ins | DevRev" }, { - "id": "ART-1977_KNOWLEDGE_NODE-25", - "text": "Average CSAT rating for ticket Owners.\\n* **SLA breaches by Customer tier**\\n\\n Number of Tickets with SLA breaches for ticket owners.\\n* **Active Tickets**\\n\\n A distribution of tickets in Open and In Progress states and the respective owners.\\n* **Closed Tickets**\\n\\n A distribution of tickets in Closed state and the respective owners.\\n* **SLA breaches**\\n\\n Number of Tickets with SLA breaches for ticket owners.\\n* **Tickets Escalated**\\n\\n Number of tickets that are escalated by", - "title": "Ticket-Team Performance | Support analytics | Computer for Support Teams | DevRev" + "id": "ART-15716_KNOWLEDGE_NODE-34", + "text": "DevRev provides dashboards for CSAT (Customer Satisfaction) scores:\\n\\nClick the Explore Section and search for the Ticket Insights or Ticket Team Performance Dashboard\\n\\nNavigate to find the CSAT widgets.\\n\\nYou can filter by time, team, or agent to get detailed insights.\\n\\nThis gives you a centralized view of customer feedback trends.3. Visualizing Data Using Dashboards and Widgets\\n\\nTo create dashboards:\\n\\nGo to the Vista you are interested in visualizing\\n\\nApply the necessary", + "title": "Support queries related playbook" }, { - "id": "ART-2011_KNOWLEDGE_NODE-4", - "text": "insights](/docs/dashboards/conversation-insights)\\n - [Conversation-SLA Analytics](/docs/dashboards/conversation-sla-analytics)\\n - [Conversation-Team Performance](/docs/dashboards/conversation-team-performance)\\n - [Ticket insights](/docs/dashboards/ticket-insights)\\n - [Ticket-SLA Analytics](/docs/dashboards/ticket-sla-analytics)\\n - [Ticket-Team Performance](/docs/dashboards/ticket-team-performance)\\n + [Conversations](/docs/product/conversation)\\n\\n - [Conversation to", - "title": "CSAT on ticket | Automate | Snap-ins | DevRev" + "id": "ART-1003_KNOWLEDGE_NODE-23", + "text": "CURRENT_DATE);\\n-- NOTE: Replace @period with 'DAY', 'WEEK', 'MONTH', or 'QUARTER'.\\n\\n\\nTicket Backlog\\n\\n\\n Definition\\n \\n The number of unresolved support tickets at any given time, which can indicate workload and efficiency issues.\\n \\n \\n Calculation\\n \\n (Total number of open tickets) - (Total number of tickets closed during a specific period)\\n \\n \\n\\n\\nSELECT (COUNT(*) - (SELECT COUNT(*) FROM tickets WHERE status = 'closed' AND EXTRACT(@period FROM created_at)", + "title": "Understanding a Support Lead's Pain Points and KPIs" } ] }, @@ -4540,18 +4540,13 @@ "query": "save filters in support portal", "retrievals": [ { - "id": "ART-1978_KNOWLEDGE_NODE-11", - "text": "[CSV comments uploader](/docs/automations/csv-comments-uploader)\\n - [CSV commands uploader](/docs/automations/csv-commands-uploader)\\n - [Descope identity validation](/docs/automations/descope-identity-validation)\\n - [Effort logger](/docs/automations/effort-logger)\\n - [HTTP archive file upload & sanitization](/docs/automations/har-sanitization)\\n - [Link preview](/docs/automations/link-preview)\\n - [Org tags sync](/docs/automations/org-tags-sync)\\n - [Search", - "title": "Customer portal | Computer for Support Teams | DevRev" - }, - { - "id": "ART-15716_KNOWLEDGE_NODE-35", - "text": "filters\\n\\nYou can create a simple report by clicking on the Smart Icon at the top right corner and selecting \\'Create New report.\\' Create a dashboard and a widget by giving a name. Select the dimensions and measures and finalize the visualization of the widget and click on the preview widget to test it out.\\n\\nEach widget can be customized with filters, groupings, and visualizations (charts, tables, etc.)4. Create a dashboard for tracking ticket resolution time\\n\\nCreate a new dashboard in", - "title": "Support queries related playbook" + "id": "ART-10697_KNOWLEDGE_NODE-31", + "text": "boosting engagement and reducing repetitive inquiries. To enable Plug, go to **Settings > Portal Settings**, activate Plug widget, and **Save** and **Publish**.\\n\\n![]()\\xc2\\xa0For more information about *Support App*, refer to the following articles: \\xe2\\x80\\xa3 [Support snap-ins | Support](/docs/product/snapins-support) \\xe2\\x80\\xa3 [Support best practices | Support](/docs/product/support-bp) \\xe2\\x80\\xa3 [Support](/docs/product/support) \\xe2\\x80\\xa3", + "title": "February 2025 | Changelog | DevRev" }, { "id": "ART-1978_KNOWLEDGE_NODE-37", - "text": "portal\\n-----------------------------\\n\\nYou can customize the look of your support portal to match your branding goals.\\n\\n1. Go to **Settings** > **Plug & Portal** > **Portal Settings**.\\n2. Under **Configuration**, enter your site name and upload your company logo.\\n * (Optional) Enable the footer and add your social media and text links in their respective fields.\\n * (Optional) Enable **Search** to get answers in search results.\\n * (Optional) Enable Plug widget to facilitate", + "text": "portal\\n-----------------------------\\n\\nYou can customize the look of your support portal to match your branding goals.\\n\\n1. Go to **Settings** > **Plug & Portal** > **Portal Settings**.\\n2. Under **Configuration**, enter your site name and upload your company logo.\\n * (Optional) Enable the footer and add your social media and text links in their respective fields.\\n * (Optional) Enable **Search** to get answers in search results.\\n * (Optional) Enable Plug widget to facilitate", "title": "Customer portal | Computer for Support Teams | DevRev" }, { @@ -4560,34 +4555,39 @@ "title": "February 2025 | Changelog | DevRev" }, { - "id": "ART-1452_KNOWLEDGE_NODE-4", - "text": "users.\\n\\nstageobjectOptional\\n\\nThe filter for stages.\\n\\nShow property\\n\\nstaged_infoobjectOptional\\n\\nShow property\\n\\nstatelist of stringsOptional\\n\\nFilters for work with any of the provided states.\\n\\nsync_metadataobjectOptional\\n\\nShow 4 properties\\n\\ntagslist of stringsOptional\\n\\nFilters for work with any of the provided tags.\\n\\ntarget_close_dateobjectOptional\\n\\nProvides ways to specify date ranges on objects.\\n\\nShow 2 variants\\n\\nticketobjectOptional\\n\\nShow 13 properties\\n\\n###", - "title": "Export Works (POST) \u2014 DevRev | Docs" + "id": "ART-1978_KNOWLEDGE_NODE-31", + "text": "only.\\n\\nThe customer portal is SEO-compatible, enhancing its discoverability so end customers can find answers directly through search engines, even before contacting support.\\n\\nKey highlights:\\n\\n* Search engine indexing - Public articles are discoverable by search engines like Google.\\n* Meta tags - The article title is used as the title tag, and the article description serves as the meta description for the article.\\n\\nGet started\\n-----------\\n\\n* Your customer portal is by default hosted", + "title": "Customer portal | Computer for Support Teams | DevRev" }, { - "id": "ART-1952_KNOWLEDGE_NODE-34", - "text": "filters from your vista will be transferred to your widget definition. If any filters are not carried over, a message will indicate the reason, and you will have the option to add the missing vista filters to your widget filter definition.\\n* **Widget Filters**: These filters are for your widget definition and include all filters from the vista, as well as other objects.\\n\\n![]()\\n\\nThe filters and dimensions are interlinked. To have filterable values, you must select them in dimensions as", - "title": "Vista Reports | Vistas | Computer by DevRev | DevRev" + "id": "ART-1978_KNOWLEDGE_NODE-27", + "text": "portal\\n-------------------------------------\\n\\n* **Enhanced customer experience**: Customers can access self-service options, track their tickets, and receive timely updates, leading to improved satisfaction.\\n* **Efficient ticket management**: The portal streamlines the ticket creation, assignment, and tracking process, ensuring faster resolution times.\\n* **Seamless, timely, and transparent communication**: Customers and support teams can engage in threaded conversations within the portal,", + "title": "Customer portal | Computer for Support Teams | DevRev" }, { - "id": "ART-10697_KNOWLEDGE_NODE-31", - "text": "boosting engagement and reducing repetitive inquiries. To enable Plug, go to **Settings > Portal Settings**, activate Plug widget, and **Save** and **Publish**.\\n\\n![]()\\xc2\\xa0For more information about *Support App*, refer to the following articles: \\xe2\\x80\\xa3 [Support snap-ins | Support](/docs/product/snapins-support) \\xe2\\x80\\xa3 [Support best practices | Support](/docs/product/support-bp) \\xe2\\x80\\xa3 [Support](/docs/product/support) \\xe2\\x80\\xa3", - "title": "February 2025 | Changelog | DevRev" + "id": "ART-1978_KNOWLEDGE_NODE-32", + "text": "on the following URL: support.devrev.ai/.\\n* Your customers can log in on the portal by entering their registered email address and OTP sent to that email address.\\n\\n![]()\\n\\n### Customer roles and permissions\\n\\nThe customer portal has two levels of customer roles and permissions:\\n\\n* **Verified customers**: Customers who can log in on the portal and see the tickets that they have created.\\n* **Customer admins**: Customers who can log in on the portal and see not just their own", + "title": "Customer portal | Computer for Support Teams | DevRev" }, { - "id": "ART-1978_KNOWLEDGE_NODE-10", - "text": "data](/docs/automations/bulk-delete)\\n - [Bulk work item uploader](/docs/automations/bulk-upload)\\n - [Commands surface expander](/docs/automations/commands-surface-expander)\\n - [Convergence](/docs/automations/converge)\\n - [Conversation reminder](/docs/automations/conversation-reminder)\\n - [CSAT on conversation](/docs/automations/csat-conv)\\n - [CSAT on ticket](/docs/automations/csat-tickets)\\n - [CSV work item uploader](/docs/automations/csv-work-item-uploader)\\n -", + "id": "ART-1978_KNOWLEDGE_NODE-0", + "text": "b\"Customer portal | Computer for Support Teams | DevRev\\n\\n* Computer\\n* Resources\\n* [Our Customers](/case-study)\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](/request-a-demo)\\n\\nComputer\\n\\nResources\\n\\n[Our Customers](/case-study)\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](/request-a-demo)\\n\\nSearch\\n\\n`CTRL`\\xc2\\xa0+\\xc2\\xa0`K`\\n\\n* [Introduction](/docs)\\n* [Computer by DevRev](/docs/intro)\\n\\n + [Core concepts](/docs/product/core)\\n + [Apps](/docs/product/apps)\\n +", "title": "Customer portal | Computer for Support Teams | DevRev" }, { - "id": "ART-1978_KNOWLEDGE_NODE-27", - "text": "portal\\n-------------------------------------\\n\\n* **Enhanced customer experience**: Customers can access self-service options, track their tickets, and receive timely updates, leading to improved satisfaction.\\n* **Efficient ticket management**: The portal streamlines the ticket creation, assignment, and tracking process, ensuring faster resolution times.\\n* **Seamless, timely, and transparent communication**: Customers and support teams can engage in threaded conversations within the portal,", - "title": "Customer portal | Computer for Support Teams | DevRev" + "id": "ART-1547_KNOWLEDGE_NODE-519", + "text": "Optional\\n\\nFilters for works with selected sync statuses.\\n\\nAllowed values: failed succeeded\\nsync_metadata.last_sync_out.sync_unit string Optional\\n\\nFilters for works modified with selected sync units.\\n\\nsync_metadata.origin_system string Optional\\n\\nFilters for issues synced from this specific origin system.\\n\\ntags string Optional\\n\\nFilters for work with any of the provided tags.\\n\\nticket.channels enum Optional\\n\\nFilters for tickets with any of the provided channels.\\n\\nAllowed", + "title": "Get Post (Beta) \u2014 DevRev | Docs" }, { - "id": "ART-1978_KNOWLEDGE_NODE-13", - "text": "group](/docs/automations/set-user-preference)\\n - [SLA status change Slack notifier](/docs/automations/sla-change-notifier)\\n - [Slash commands](/docs/automations/slash-commands)\\n - [Spam Shield](/docs/automations/spam-shield)\\n - [Subtype Migration](/docs/automations/subtype-migration)\\n - [Ticket age in engineering](/docs/automations/ticket-age-in-engineering)\\n - [Ticket issue field migrator](/docs/automations/ticket-issue-field-migrator)\\n - [Ticket", - "title": "Customer portal | Computer for Support Teams | DevRev" + "id": "ART-1543_KNOWLEDGE_NODE-517", + "text": "Optional\\n\\nFilters for works with selected sync statuses.\\n\\nAllowed values: failed succeeded\\nsync_metadata.last_sync_out.sync_unit string Optional\\n\\nFilters for works modified with selected sync units.\\n\\nsync_metadata.origin_system string Optional\\n\\nFilters for issues synced from this specific origin system.\\n\\ntags string Optional\\n\\nFilters for work with any of the provided tags.\\n\\nticket.channels enum Optional\\n\\nFilters for tickets with any of the provided channels.\\n\\nAllowed", + "title": "Metric Definitions List Post (Beta) \u2014 DevRev | Docs" + }, + { + "id": "ART-1562_KNOWLEDGE_NODE-519", + "text": "Optional\\n\\nFilters for works with selected sync statuses.\\n\\nAllowed values: failed succeeded\\nsync_metadata.last_sync_out.sync_unit string Optional\\n\\nFilters for works modified with selected sync units.\\n\\nsync_metadata.origin_system string Optional\\n\\nFilters for issues synced from this specific origin system.\\n\\ntags string Optional\\n\\nFilters for work with any of the provided tags.\\n\\nticket.channels enum Optional\\n\\nFilters for tickets with any of the provided channels.\\n\\nAllowed", + "title": "Get (Beta) \u2014 DevRev | Docs" } ] }, @@ -4596,54 +4596,54 @@ "query": "unable to convert conversation into ticket and can't fill customer information", "retrievals": [ { - "id": "ART-4271_KNOWLEDGE_NODE-26", - "text": "conversation metadata including: \\n * Source channel\\n * Customer account information\\n * External members added as **reported by** on the ticket\\n * An AI-generated ticket title and description based on customer messages.\\n\\n### How to convert Conversations to Tickets\\n\\n**Manual Conversion**\\n\\nTo manually convert a conversation to a ticket:\\n\\n 1. Open the conversation record pane view.\\n 2. Click **Convert to Ticket** to initiate the conversion.\\n\\n**Automated Conversion", - "title": "Convert Conversations to Tickets | Conversations | Support | DevRev" + "id": "ART-6174_KNOWLEDGE_NODE-28", + "text": "tickets\\n--------------------------------\\n\\n**Manual conversion**\\n\\nGo to the conversation record pane and select **Convert to Ticket** to create a new ticket from the conversation.\\n\\n![]()\\n\\n**Automated conversion via workflows**\\n\\nSet up automated [workflows](./workflow-engine) to convert conversations to tickets based on specific triggers:\\n\\n* When a conversation meets defined criteria\\n* When the AI agent identifies an issue requiring escalation\\n* According to custom business", + "title": "Conversation to ticket conversion | Conversations | Computer for Support Teams | DevRev" }, { - "id": "ART-4271_KNOWLEDGE_NODE-31", - "text": "AI-handled conversation reaches its capability limits and needs human expertise.\\n * **Extended troubleshooting** : Issues requiring multiple steps or follow-ups over time.\\n\\n## Key information\\n\\n * **Channel support** : Currently, the conversion feature is only available for PLuG and Slack conversations. Other channels still use the traditional **Link Ticket** functionality.\\n\\n * **CSAT surveys** : CSAT surveys are not sent when a conversation is converted to a ticket. Surveys are only", + "id": "ART-4271_KNOWLEDGE_NODE-24", + "text": "[Support](/docs/product/support?)\\n 4. [Conversations](/docs/product/conversation?)\\n 5. [Convert Conversations to Tickets](/docs/product/Conversation-Tickets?)\\n\\n# Convert Conversations to Tickets\\n\\nYou can now convert conversations from PLuG and Slack directly into tickets. Previously, conversations were only linked to tickets. This update streamlines workflows and enhances the customer experience.\\n\\nFor conversations originating from PLuG or Slack, the **Link to Ticket** functionality", "title": "Convert Conversations to Tickets | Conversations | Support | DevRev" }, { - "id": "ART-6174_KNOWLEDGE_NODE-28", - "text": "tickets\\n--------------------------------\\n\\n**Manual conversion**\\n\\nGo to the conversation record pane and select **Convert to Ticket** to create a new ticket from the conversation.\\n\\n![]()\\n\\n**Automated conversion via workflows**\\n\\nSet up automated [workflows](./workflow-engine) to convert conversations to tickets based on specific triggers:\\n\\n* When a conversation meets defined criteria\\n* When the AI agent identifies an issue requiring escalation\\n* According to custom business", - "title": "Conversation to ticket conversion | Conversations | Computer for Support Teams | DevRev" + "id": "ART-4271_KNOWLEDGE_NODE-25", + "text": "is being replaced with a new **Convert to Ticket** feature. This change provides a more seamless transition from conversation to ticket management.\\n\\n## How Conversation conversion works\\n\\nWhen you convert a conversation to a ticket, the following happens automatically:\\n\\n * The original conversation is moved to _Archived_ stage and cannot be reopened.\\n * A new ticket is created with: \\n * All internal discussions and customer messages copied from the conversation.\\n * Preserved", + "title": "Convert Conversations to Tickets | Conversations | Support | DevRev" }, { - "id": "ART-6174_KNOWLEDGE_NODE-26", - "text": "functionality is replaced with a new **Convert to Ticket** feature. Currently, the conversion feature is available only for Plug and Slack conversations. Other channels still use the traditional **Link Ticket** functionality.\\n\\nConversion cannot be undone. Once a conversation is converted to a ticket, this action is permanent and the conversation remains archived.\\n\\nConversation conversion process\\n-------------------------------\\n\\nWhen you convert a conversation to a ticket, the following", - "title": "Conversation to ticket conversion | Conversations | Computer for Support Teams | DevRev" + "id": "ART-4271_KNOWLEDGE_NODE-26", + "text": "conversation metadata including: \\n * Source channel\\n * Customer account information\\n * External members added as **reported by** on the ticket\\n * An AI-generated ticket title and description based on customer messages.\\n\\n### How to convert Conversations to Tickets\\n\\n**Manual Conversion**\\n\\nTo manually convert a conversation to a ticket:\\n\\n 1. Open the conversation record pane view.\\n 2. Click **Convert to Ticket** to initiate the conversion.\\n\\n**Automated Conversion", + "title": "Convert Conversations to Tickets | Conversations | Support | DevRev" }, { - "id": "ART-4271_KNOWLEDGE_NODE-29", - "text": "end user.\\n\\n## Why you should convert a Conversation to a Ticket\\n\\nConsider converting a conversation to a ticket in these scenarios:\\n\\n * **Complex issues** : When a customer inquiry requires in-depth investigation that can't be resolved in a quick conversation.\\n * **Cross-team collaboration** : Issues requiring input from multiple departments or specialists.\\n * **Escalation needs** : When a conversation needs to be escalated to a higher support tier.\\n * **Feature requests** :", - "title": "Convert Conversations to Tickets | Conversations | Support | DevRev" + "id": "ART-15716_KNOWLEDGE_NODE-7", + "text": "Tickets from Chat ConversationsYes, you can create a ticket from a conversation without leaving the chat. Some fields may be prefilled from the conversation.\\n\\nDetails:\\xc2\\xa0[Conv \\xe2\\x86\\x92 Ticket Creation](https://devrev.ai/docs/product/conversation-ticket)\\n\\n5. Viewing Ticket Activity to Avoid Duplicate Responses\\n\\nCurrently, there\\xe2\\x80\\x99s no direct feature to see who is viewing a ticket in real time. But, we can see if someone is typing on a ticket.\\n\\n6. Generating AI Summaries", + "title": "Support queries related playbook" }, { - "id": "ART-6174_KNOWLEDGE_NODE-27", - "text": "happens automatically:\\n\\n* The original conversation moves to *Archived* stage and cannot be reopened.\\n* A new ticket is created with:\\n + All internal discussions and customer messages copied from the conversation\\n + Equivalent metadata as the conversation, including source channel, customer account information, and external members added as **reported by** on the ticket\\n + An AI-generated ticket title and description based on customer messages\\n\\nConvert conversations to", + "id": "ART-6174_KNOWLEDGE_NODE-0", + "text": "b\"Conversation to ticket conversion | Conversations | Computer for Support Teams | DevRev\\n\\n* Computer\\n* Resources\\n* [Our Customers](/case-study)\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](/request-a-demo)\\n\\nComputer\\n\\nResources\\n\\n[Our Customers](/case-study)\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](/request-a-demo)\\n\\nSearch\\n\\n`CMD`\\xc2\\xa0+\\xc2\\xa0`K`\\n\\n* [Introduction](/docs)\\n* [Computer by DevRev](/docs/intro)\\n\\n + [Core concepts](/docs/product/core)\\n +", "title": "Conversation to ticket conversion | Conversations | Computer for Support Teams | DevRev" }, { - "id": "ART-6174_KNOWLEDGE_NODE-31", - "text": "Cross-team collaboration needs\\n* Escalation requirements\\n* Feature requests\\n* Bug reports\\n* SLA tracking requirements\\n* Documentation needs\\n* Resource allocation requirements\\n* AI capability limitations\\n* Extended troubleshooting needs\\n\\nSupport workflows\\n-----------------\\n\\n* **CSAT surveys**: CSAT surveys are not sent when a conversation is converted to a ticket. Surveys are only triggered when a conversation is resolved, not when it's archived through conversion.\\n* **SLA", - "title": "Conversation to ticket conversion | Conversations | Computer for Support Teams | DevRev" + "id": "ART-2024_KNOWLEDGE_NODE-27", + "text": "help now... ask again in 5d\\n\\nSample response:\\n\\n> I am unable to assist you at the moment, however please reach out to me again in five days and I will be happy to help you.\\n\\n### Summarize\\n\\nUsing the summarize command, you can sum up the entire conversation. It applies to the following:\\n\\n* Conversation\\n* Tickets\\n* Issues\\n* Part\\n* Workspace\\n* Customer\\n* Account\\n\\nSample response:\\n\\n> **Summary:**\\n>\\n> * Rahul from DummyOrg is having difficulty installing the Plug Widget.\\n> *", + "title": "Slash commands | Automate | Snap-ins | DevRev" }, { - "id": "ART-6174_KNOWLEDGE_NODE-32", - "text": "handling**: Conversation and ticket SLAs operate independently. When converting:\\n\\n + The new ticket starts with its own response and resolution SLA timers\\n + All active SLA metrics on the original conversation are marked as completed\\n\\n[PreviousConversations](/docs/product/conversation)[NextTickets](/docs/product/tickets)\\n\\n#### On this page\\n\\n* [Conversation conversion process](#conversation-conversion-process)\\n* [Convert conversations to tickets](#convert-conversations-to-tickets)\\n*", - "title": "Conversation to ticket conversion | Conversations | Computer for Support Teams | DevRev" + "id": "ART-4271_KNOWLEDGE_NODE-27", + "text": "via Workflows**\\n\\nSet up automated workflows to convert conversations to tickets based on specific triggers:\\n\\n * When a conversation is updated with certain criteria\\n * When your AI agent identifies an issue requiring escalation\\n * According to your custom business rules\\n\\nWorkflows enable seamless handovers from automated conversations to your support teams when necessary.\\n\\n## End user experience\\n\\n### PLuG widget experience\\n\\nWhen a conversation is converted to a ticket in the", + "title": "Convert Conversations to Tickets | Conversations | Support | DevRev" }, { - "id": "ART-6174_KNOWLEDGE_NODE-30", - "text": "there.\\n\\n![]()\\n\\nSlack end-user experience\\n-------------------------\\n\\nWhen a conversation is converted to a ticket in Slack:\\n\\n* Ticket information appears within the same thread.\\n* All subsequent messages sync with the newly created ticket.\\n* The transition is seamless for the end user.\\n\\nConversation conversion scenarios\\n---------------------------------\\n\\nConsider converting a conversation to a ticket in these scenarios:\\n\\n* Complex issues requiring in-depth investigation\\n*", - "title": "Conversation to ticket conversion | Conversations | Computer for Support Teams | DevRev" + "id": "ART-4271_KNOWLEDGE_NODE-29", + "text": "end user.\\n\\n## Why you should convert a Conversation to a Ticket\\n\\nConsider converting a conversation to a ticket in these scenarios:\\n\\n * **Complex issues** : When a customer inquiry requires in-depth investigation that can't be resolved in a quick conversation.\\n * **Cross-team collaboration** : Issues requiring input from multiple departments or specialists.\\n * **Escalation needs** : When a conversation needs to be escalated to a higher support tier.\\n * **Feature requests** :", + "title": "Convert Conversations to Tickets | Conversations | Support | DevRev" }, { - "id": "ART-6174_KNOWLEDGE_NODE-24", - "text": "[Product demos](/docs/DevRevU/demos)\\n\\nOn this page\\n\\n* [Conversation conversion process](#conversation-conversion-process)\\n* [Convert conversations to tickets](#convert-conversations-to-tickets)\\n* [Plug widget end-user experience](#plug-widget-enduser-experience)\\n* [Slack end-user experience](#slack-enduser-experience)\\n* [Conversation conversion scenarios](#conversation-conversion-scenarios)\\n* [Support workflows](#support-workflows)\\n\\n1. [Documentation](/docs)\\n3. [Computer for Support", - "title": "Conversation to ticket conversion | Conversations | Computer for Support Teams | DevRev" + "id": "ART-2035_KNOWLEDGE_NODE-38", + "text": "recommended if you already have a conversation in progress. Configure the snap-in to send or not send a ticket summary card to the Slack thread using the **Notify on conversation to ticket conversion** setting. Regardless, the Slack thread will sync with the new ticket instead of the ongoing conversation.\\n\\n![]()\\n\\nSlack does not support slash commands in threads.\\n\\nChoosing one of the first two options will open a pop-up modal with the new ticket form. Complete the required fields; some", + "title": "Slack | Integrate | Snap-ins | DevRev" } ] }, @@ -4652,54 +4652,54 @@ "query": "control email notifications for new conversation", "retrievals": [ { - "id": "ART-1953_KNOWLEDGE_NODE-30", - "text": "linked to a conversation\\n-------------------------------\\n\\n* **Trigger**: A ticket is linked to an existing conversation.\\n* **Action**: The system sends out a notification with the linked ticket number.\\n* **Sender**: {Company\\\\_Name} [support@yourdomain.com](mailto:support@yourdomain.com)\\n* **Subject**: \"\"\\n\\n![]()\\n\\nThis email is only sent to the organizations with [Convergence snap-in](https://docs.devrev.ai/automations/converge)\\n\\nChange of", + "id": "ART-1953_KNOWLEDGE_NODE-28", + "text": "**Configure** > **Notification Sender Email Address** and select the required option.\\n\\nReply to the customer on a conversation\\n---------------------------------------\\n\\n* **Trigger**: When a reply is made to a customer on a conversation and they are not online anymore.\\n* **Action**: The system sends out a notification to the customer with the recent messages while highlighting the latest message that triggered the email.\\n* **Sender**: {Sender\\\\_Name}", "title": "Customer email notifications | Computer by DevRev | DevRev" }, { - "id": "ART-1953_KNOWLEDGE_NODE-27", - "text": "conversation, ensuring seamless and continuous communication.\\n\\nBy default, notifications are sent from [notifications@devrev.ai](mailto:notifications@devrev.ai). However, this setting can be overridden to use the organization\\xe2\\x80\\x99s primary email address as the sender, or notifications can be turned off entirely.\\n\\nTo configure the notifications setting, under [**Settings** > **Snap-ins** > **Email Integration**](https://app.devrev.ai/devrev/settings/snap-ins/email-with-tickets), go to", - "title": "Customer email notifications | Computer by DevRev | DevRev" + "id": "ART-2015_KNOWLEDGE_NODE-29", + "text": "the user during OTP collection.\\n * Customize the message that is shown to the user on successful verification\\n of email.\\n * You can trigger this either for all new conversations from an unverified\\n user or when Computer is unable to deflect a conversation.\\n\\n + To activate the automation for every new conversation, toggle on **Send\\n on Create**.\\n + If you prefer the automation to only be triggered when Computer is unable\\n to deflect a conversation, make", + "title": "Descope identity validation | Automate | Snap-ins | DevRev" }, { - "id": "ART-1953_KNOWLEDGE_NODE-32", - "text": "\\xe2\\x80\\x9cUpdate on your Conversation with {Company\\\\_Name}\"\\n\\n![]()\\n\\nThis email is only sent to organizations that have installed [Convergence snap-in](https://docs.devrev.ai/automations/converge).\\n\\nCSAT survey for conversation/ticket\\n-----------------------------------\\n\\n* **Trigger**: A CSAT survey is sent for a conversation or ticket.\\n* **Action**: The system sends out a notification with the ticket/conversation number and CSAT form.\\n* **Sender**: DevRev", + "id": "ART-1953_KNOWLEDGE_NODE-27", + "text": "conversation, ensuring seamless and continuous communication.\\n\\nBy default, notifications are sent from [notifications@devrev.ai](mailto:notifications@devrev.ai). However, this setting can be overridden to use the organization\\xe2\\x80\\x99s primary email address as the sender, or notifications can be turned off entirely.\\n\\nTo configure the notifications setting, under [**Settings** > **Snap-ins** > **Email Integration**](https://app.devrev.ai/devrev/settings/snap-ins/email-with-tickets), go to", "title": "Customer email notifications | Computer by DevRev | DevRev" }, { - "id": "ART-1953_KNOWLEDGE_NODE-28", - "text": "**Configure** > **Notification Sender Email Address** and select the required option.\\n\\nReply to the customer on a conversation\\n---------------------------------------\\n\\n* **Trigger**: When a reply is made to a customer on a conversation and they are not online anymore.\\n* **Action**: The system sends out a notification to the customer with the recent messages while highlighting the latest message that triggered the email.\\n* **Sender**: {Sender\\\\_Name}", - "title": "Customer email notifications | Computer by DevRev | DevRev" + "id": "ART-3068_KNOWLEDGE_NODE-24", + "text": "[Documentation](/docs)\\n3. [Snap-ins](/docs/snapins)\\n[Automate](/docs/automate)\\n[Conversation reminder](/docs/automations/conversation-reminder)\\n\\nConversation reminder\\n=====================\\n\\nThe Conversation Reminder Snap-in is designed to automatically send a\\nnotification to the customer who initiated the conversation if it remains in\\n\"Waiting on User\" stage for an extended period, as defined in the configured\\ntime settings. The notification message sent to the customer can be", + "title": "Conversation reminder | Automate | Snap-ins | DevRev" }, { - "id": "ART-1953_KNOWLEDGE_NODE-31", - "text": "stage of a ticket/conversation\\n----------------------------------------\\n\\n* **Trigger**: When there\\'s a change of stage in a ticket or conversation.\\n* **Action**: The system sends out a notification detailing the Ticket/Conversation number and stage change.\\n* **Sender**: {Company\\\\_Name} [support@yourdomain.com](mailto:support@yourdomain.com)\\n* **Subject**:\\n + For ticket: \"[{Company\\\\_Name}] Update on TKT-XXX - Ticket Title\"\"\"\\n + For conversations:", - "title": "Customer email notifications | Computer by DevRev | DevRev" + "id": "ART-1983_KNOWLEDGE_NODE-30", + "text": "creation, go to **Settings** > **Turing** > **Q&As** > **Preferences** on the top right and enable **Auto generate Q&As** and click **Save**.\\n\\n![]()\\n\\nYou need to be an admin to set preferences.\\n\\n![]()\\n\\nWhen Computer creates a new Q&A, the conversation's owner receives a notification. It's their chance to ensure accuracy before deciding whether to *Publish* them if needed or *Archive* if not.\\n\\nOnce approved and published, these Q&As enter Computer's knowledge base, ready to tackle", + "title": "Questions & answers | Computer for Support Teams | DevRev" }, { - "id": "ART-1953_KNOWLEDGE_NODE-36", - "text": "conversation](#ticket-linked-to-a-conversation)\\n* [Change of stage of a ticket/conversation](#change-of-stage-of-a-ticketconversation)\\n* [CSAT survey for conversation/ticket](#csat-survey-for-conversationticket)\\n* [Auto customer reply](#auto-customer-reply)\\n* [Auto reply on email](#auto-reply-on-email)\\n\\n[Enterprise grade security to protect customer data\\n\\nLearn more about it.\\n\\n![]()](/blog/soc-compliance)\\n\\nComputer\\n\\n* [Meet Computer](/meet-computer)\\n* [How Computer", + "id": "ART-1953_KNOWLEDGE_NODE-30", + "text": "linked to a conversation\\n-------------------------------\\n\\n* **Trigger**: A ticket is linked to an existing conversation.\\n* **Action**: The system sends out a notification with the linked ticket number.\\n* **Sender**: {Company\\\\_Name} [support@yourdomain.com](mailto:support@yourdomain.com)\\n* **Subject**: \"\"\\n\\n![]()\\n\\nThis email is only sent to the organizations with [Convergence snap-in](https://docs.devrev.ai/automations/converge)\\n\\nChange of", "title": "Customer email notifications | Computer by DevRev | DevRev" }, { - "id": "ART-1953_KNOWLEDGE_NODE-4", - "text": "insights](/docs/dashboards/conversation-insights)\\n - [Conversation-SLA Analytics](/docs/dashboards/conversation-sla-analytics)\\n - [Conversation-Team Performance](/docs/dashboards/conversation-team-performance)\\n - [Ticket insights](/docs/dashboards/ticket-insights)\\n - [Ticket-SLA Analytics](/docs/dashboards/ticket-sla-analytics)\\n - [Ticket-Team Performance](/docs/dashboards/ticket-team-performance)\\n + [Conversations](/docs/product/conversation)\\n\\n - [Conversation to", - "title": "Customer email notifications | Computer by DevRev | DevRev" + "id": "ART-2035_KNOWLEDGE_NODE-36", + "text": "Slack Channel ID in the **Channel ID to send conversation notifications** snap-in configuration as the target to post notifications.\\n\\n* Any new message within tickets in the customer messages panel is also subjected to the same automation.\\n* To prevent notification overload, each conversation or ticket is subject to a five minute cooldown period between notifications. Multiple consecutive messages within this window will not trigger additional notifications.\\n* Notification threads are not", + "title": "Slack | Integrate | Snap-ins | DevRev" }, { - "id": "ART-1953_KNOWLEDGE_NODE-24", - "text": "conversation](#reply-to-the-customer-on-a-conversation)\\n* [Reply to the customer on a ticket](#reply-to-the-customer-on-a-ticket)\\n* [Ticket linked to a conversation](#ticket-linked-to-a-conversation)\\n* [Change of stage of a ticket/conversation](#change-of-stage-of-a-ticketconversation)\\n* [CSAT survey for conversation/ticket](#csat-survey-for-conversationticket)\\n* [Auto customer reply](#auto-customer-reply)\\n* [Auto reply on email](#auto-reply-on-email)\\n\\n1. [Documentation](/docs)\\n3.", - "title": "Customer email notifications | Computer by DevRev | DevRev" + "id": "ART-1790_KNOWLEDGE_NODE-83", + "text": "object.\\nnotifications list of objects Required\\nThe list of notifications to send.\\nShow variant\\nResponse.\\n\\nThis endpoint returns a map from strings to any.\\nAPI Reference conversations Create.\\n\\nPOST https:// api.devrev.ai / conversations.create\\nCreates a conversation.\\nRequest.\\n\\nThis endpoint expects an object.\\ntype \"support\" Required\\ndescription string Optional\\nDescription for the conversation.\\ngroup string Optional\\nThe group that the conversation is associated with.\\nis_spam", + "title": "List Post \u2014 DevRev | Docs" }, { - "id": "ART-1820_KNOWLEDGE_NODE-3", - "text": "Error\\n\\nWas this page helpful?\\n\\nYesNo\\n\\n[Previous](/beta/api-reference/notifications/content-template-list-post)[#### Create Conversation\\n\\nNext](/beta/api-reference/conversations/create)[Built with](https://buildwithfern.com/?utm_campaign=buildWith&utm_medium=docs&utm_source=developer.devrev.ai)'", - "title": "Send Notifications | DevRev | Docs" + "id": "ART-1954_KNOWLEDGE_NODE-24", + "text": "triaging](#filters-and-tools-for-triaging)\\n* [Notification priorities and channels](#notification-priorities-and-channels)\\n* [Email and push notifications](#email-and-push-notifications)\\n* [Personalizing notifications](#personalizing-notifications)\\n* [Collision and prioritization](#collision-and-prioritization)\\n* [Follow conversations](#follow-conversations)\\n* [Daily email digest](#daily-email-digest)\\n\\n1. [Documentation](/docs)\\n3. [Computer by", + "title": "Updates | Computer by DevRev | DevRev" }, { - "id": "ART-1953_KNOWLEDGE_NODE-35", - "text": "installed [Auto-reply snap-in](https://docs.devrev.ai/automations/auto-reply).\\n\\n[PreviousUpdates](/docs/product/updates)[NextRoles](/docs/product/roles)\\n\\n#### On this page\\n\\n* [White-label customer email notifications](#whitelabel-customer-email-notifications)\\n* [Reply to the customer on a conversation](#reply-to-the-customer-on-a-conversation)\\n* [Reply to the customer on a ticket](#reply-to-the-customer-on-a-ticket)\\n* [Ticket linked to a", - "title": "Customer email notifications | Computer by DevRev | DevRev" + "id": "ART-1954_KNOWLEDGE_NODE-38", + "text": "triaging](#filters-and-tools-for-triaging)\\n* [Notification priorities and channels](#notification-priorities-and-channels)\\n* [Email and push notifications](#email-and-push-notifications)\\n* [Personalizing notifications](#personalizing-notifications)\\n* [Collision and prioritization](#collision-and-prioritization)\\n* [Follow conversations](#follow-conversations)\\n* [Daily email digest](#daily-email-digest)\\n\\n[Enterprise grade security to protect customer data\\n\\nLearn more about", + "title": "Updates | Computer by DevRev | DevRev" } ] }, @@ -4709,7 +4709,7 @@ "retrievals": [ { "id": "ART-15688_KNOWLEDGE_NODE-29", - "text": "system automatically validates:\\n\\n * Date format and range (within last 10 days to next 10 days)\\n * Hours and minutes values\\n * Prevents logging when both hours and minutes are zero\\n3. **Confirmation**: After successful validation, the effort is logged and a confirmation message appears in the timeline.\\n\\nSupported object types\\n----------------------\\n\\nThe Effort logger snap-in works with the following object types:\\n\\n* **Tickets**: Log effort against support tickets, bug reports,", + "text": "system automatically validates:\\n\\n * Date format and range (within last 10 days to next 10 days)\\n * Hours and minutes values\\n * Prevents logging when both hours and minutes are zero\\n3. **Confirmation**: After successful validation, the effort is logged and a confirmation message appears in the timeline.\\n\\nSupported object types\\n----------------------\\n\\nThe Effort logger snap-in works with the following object types:\\n\\n* **Tickets**: Log effort against support tickets, bug reports,", "title": "Effort logger | Automate | Snap-ins | DevRev" }, { @@ -4718,44 +4718,44 @@ "title": "Ticket age in engineering | Automate | Snap-ins | DevRev" }, { - "id": "ART-2021_KNOWLEDGE_NODE-25", - "text": "spent on engineering for that ticket. There can be multiple engineering\\nsessions. An engineering session starts when a ticket moves from a\\nnon-engineering stage to an engineering stage and it ends when it moves from an\\nengineering stage to a non-engineering stage. You should select which ticket\\nstages reflect engineering work and if the time spent should be shown in hours\\nor days.\\n\\nInstalling the Ticket age in engineering snap-in\\n------------------------------------------------\\n\\n1.", - "title": "Ticket age in engineering | Automate | Snap-ins | DevRev" + "id": "ART-2028_KNOWLEDGE_NODE-24", + "text": "[Snap-ins](/docs/snapins)\\n[Automate](/docs/automate)\\n[Work duration](/docs/automations/work-duration)\\n\\nWork duration\\n=============\\n\\n[Work duration](/marketplace/work-duration) offers the ability\\nto track how much work issues and tickets took to complete, measured by time\\nspent in work sessions.\\n\\nThe snap-in adds a new attribute to tickets and issues which automatically\\ncalculates the work duration for that item. Work duration is meassured in time\\nspent through work sessions. A work", + "title": "Work duration | Automate | Snap-ins | DevRev" }, { - "id": "ART-1961_KNOWLEDGE_NODE-37", - "text": "\\n{{Ticket\\xc2\\xa0Created\\xc2\\xa0>\\xc2\\xa0Output\\xc2\\xa0>\\xc2\\xa0Reported\\xc2\\xa0By\\xc2\\xa0>\\xc2\\xa0Rev\\xc2\\xa0Org\\xc2\\xa0>\\xc2\\xa0Display\\xc2\\xa0Name}}.\\xe2\\x80\\x9d\\n\\n\\n\\nDelay\\n\\n\\n\\nDuration: 2 minutes\\n\\n\\n\\nIf-else\\n\\n\\n\\nAttribute:\\xc2\\xa0Ticket\\xc2\\xa0Created/Output\\xc2\\xa0>\\xc2\\xa0Applies\\xc2\\xa0to\\xc2\\xa0part\\xc2\\xa0>\\xc2\\xa0Display\\xc2\\xa0ID \\nOperator: Equals \\nOperand: CAPL-18\\n\\n\\n\\nTicket \\ncreated\\n\\n\\n\\nEnd\\n```\\n\\n[### Workflow action", - "title": "Workflows | Computer by DevRev | DevRev" + "id": "ART-1275_KNOWLEDGE_NODE-7", + "text": "account\\xe2\\x80\\x99s display name to better reflect the\\nsnap-in\\xe2\\x80\\x99s behavior.\\n\\nmanifest.yaml\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | version: \"2\" |\\n| 2 | |\\n| 3 | name: \"Timely Ticketer\" |\\n| 4 | description: \"Snap-in to create ticket every 10 minutes\" |\\n| 5 | |\\n| 6 | service_account: |\\n| 7 | display_name: Automatic Ticket Creator Bot |\\n```\\n\\nNext, update the `event_sources` section to use the `timer-events` event source.\\nThe `timer-events` source type takes a `config` of", + "title": "Using a snap-in to perform a DevRev action | DevRev | Docs" }, { - "id": "ART-15688_KNOWLEDGE_NODE-28", - "text": "effort logs as custom objects with structured data\\n\\nHow to use\\n----------\\n\\n1. **Access the command**: In the timeline of any ticket or conversation, type the following command:\\n\\n```\\n```\\n1 /log_effort\\n```\\n```\\n\\n1. **Enter effort details**: The snap-in prompts you to enter:\\n\\n * **Date**: The date when the effort was performed (MM/DD/YYYY format)\\n * **Hours**: Number of hours worked (0 or positive number)\\n * **Minutes**: Number of minutes worked (0-59)\\n2. **Validation**: The", - "title": "Effort logger | Automate | Snap-ins | DevRev" + "id": "ART-12391_KNOWLEDGE_NODE-27", + "text": "workflow.\\n\\nNow, your workflow runs whenever a conversation or a ticket gets created and it\\nassigns it to an AI agent, which handles the conversation. No brittle rules.\\n\\nFind below a detailed explanation of all the fields needed to configure in the\\n\"Talk to Agent\" Step\\n\\n| Parameter | Type | Description |\\n| --- | --- | --- |\\n| agent | String | ID of the AI agent to use. Use the dropdown to select one. |\\n| object | String | ID of the conversation or ticket where the agent operate.s |\\n|", + "title": "Conversational workflows | Workflows | Computer by DevRev | DevRev" }, { - "id": "ART-2021_KNOWLEDGE_NODE-26", - "text": "Install the\\n [Ticket age in engineering](/marketplace/ticket-age-in-engineering)\\n from the DevRev marketplace.\\n2. Add all of the **stage names** that reflect that engineering work is planned\\n or is being done for that ticket. The stages you specify are the ones that\\n track time spent on engineering. The default values are the default DevRev\\n engineering stages for tickets.\\n3. Select whether time spent on engineering should be displayed in hours or\\n days.\\n4. Click **Install", - "title": "Ticket age in engineering | Automate | Snap-ins | DevRev" + "id": "ART-2012_KNOWLEDGE_NODE-26", + "text": "customer knows why a new ticket was created. The following fields are automatically set on the follow-up ticket based on the archived ticket:\\n\\n * **Title**\\n * **Customer**\\n * **Reported By**\\n * **Tag** is_followup In addition, the tag has_followup is added to the archived ticket.\\n\\nIf the customer responds to a ticket in the terminal stage for the second time, their message will be added to that ticket and the **Needs response** toggle will be enabled. However, no follow-up tickets", + "title": "Follow-up ticket | Automate | Snap-ins | DevRev" }, { - "id": "ART-2665_KNOWLEDGE_NODE-13", - "text": "creator](/docs/automations/smart-issue-creator)\\n - [Set user preference for group](/docs/automations/set-user-preference)\\n - [SLA status change Slack notifier](/docs/automations/sla-change-notifier)\\n - [Slash commands](/docs/automations/slash-commands)\\n - [Spam Shield](/docs/automations/spam-shield)\\n - [Subtype Migration](/docs/automations/subtype-migration)\\n - [Ticket age in engineering](/docs/automations/ticket-age-in-engineering)\\n - [Ticket issue field", - "title": "Session recording options | Session analytics | Computer for Your Customers | DevRev" + "id": "ART-1508_KNOWLEDGE_NODE-27", + "text": "for tickets that are associated with any of the brands.\\n\\nchannelslist of stringsOptional\\n\\nFilters for conversations that are associated with any of the\\nchannels.\\n\\ncustom\\\\_fieldsobjectOptional\\n\\nFilters for custom fields.\\n\\nfirstintegerOptional\\n\\nThe number of conversation items to return. The default is \\'50\\', the\\nmaximum is \\'5000\\'.\\n\\ngrouplist of stringsOptional\\n\\nFilters for conversation that belong to the given groups.\\n\\nis\\\\_creator\\\\_verifiedbooleanOptional\\n\\nFilters for", + "title": "Export Conversations | DevRev | Docs" }, { - "id": "ART-2028_KNOWLEDGE_NODE-24", - "text": "[Snap-ins](/docs/snapins)\\n[Automate](/docs/automate)\\n[Work duration](/docs/automations/work-duration)\\n\\nWork duration\\n=============\\n\\n[Work duration](/marketplace/work-duration) offers the ability\\nto track how much work issues and tickets took to complete, measured by time\\nspent in work sessions.\\n\\nThe snap-in adds a new attribute to tickets and issues which automatically\\ncalculates the work duration for that item. Work duration is meassured in time\\nspent through work sessions. A work", - "title": "Work duration | Automate | Snap-ins | DevRev" + "id": "ART-6176_KNOWLEDGE_NODE-14", + "text": "migrator](/docs/automations/ticket-issue-field-migrator)\\n - [Ticket Immutability](/docs/automations/ticket-immutability)\\n - [Ticket email notifier](/docs/automations/ticket-email-notifier)\\n - [Task tracker](/docs/automations/task-tracker)\\n - [Ticket Tagger](/docs/automations/ticket-tagger)\\n - [Tracxn sync](/docs/automations/tracxn-sync)\\n - [User group validator](/docs/automations/user-group-validator)\\n - [Work duration](/docs/automations/work-duration)\\n -", + "title": "Real-time sentiment evaluator | Automate | Snap-ins | DevRev" }, { - "id": "ART-2665_KNOWLEDGE_NODE-14", - "text": "migrator](/docs/automations/ticket-issue-field-migrator)\\n - [Ticket Immutability](/docs/automations/ticket-immutability)\\n - [Ticket email notifier](/docs/automations/ticket-email-notifier)\\n - [Task tracker](/docs/automations/task-tracker)\\n - [Ticket Tagger](/docs/automations/ticket-tagger)\\n - [Tracxn sync](/docs/automations/tracxn-sync)\\n - [User group validator](/docs/automations/user-group-validator)\\n - [Work duration](/docs/automations/work-duration)\\n -", - "title": "Session recording options | Session analytics | Computer for Your Customers | DevRev" + "id": "ART-2575_KNOWLEDGE_NODE-14", + "text": "migrator](/docs/automations/ticket-issue-field-migrator)\\n - [Ticket Immutability](/docs/automations/ticket-immutability)\\n - [Ticket email notifier](/docs/automations/ticket-email-notifier)\\n - [Task tracker](/docs/automations/task-tracker)\\n - [Ticket Tagger](/docs/automations/ticket-tagger)\\n - [Tracxn sync](/docs/automations/tracxn-sync)\\n - [User group validator](/docs/automations/user-group-validator)\\n - [Work duration](/docs/automations/work-duration)\\n -", + "title": "Account and contact import | Computer for Growth Teams | DevRev" }, { - "id": "ART-1003_KNOWLEDGE_NODE-26", - "text": "support tickets, which helps measure workload balance and resource allocation.\\n \\n \\n Calculation\\n \\n (Total hours spent on support tasks) / (Total working hours) * 100\\n \\n \\n\\n\\nSELECT (SUM(TIMESTAMPDIFF(MINUTE, t.start_time, t.end_time)) * 100) / (COUNT(DISTINCT t.engineer_id) * 8 * 60) AS AgentUtilizationRate\\nFROM ticket_work_times\\n\\n\"", - "title": "Understanding a Support Lead's Pain Points and KPIs" + "id": "ART-4186_KNOWLEDGE_NODE-14", + "text": "migrator](/docs/automations/ticket-issue-field-migrator)\\n - [Ticket Immutability](/docs/automations/ticket-immutability)\\n - [Ticket email notifier](/docs/automations/ticket-email-notifier)\\n - [Task tracker](/docs/automations/task-tracker)\\n - [Ticket Tagger](/docs/automations/ticket-tagger)\\n - [Tracxn sync](/docs/automations/tracxn-sync)\\n - [User group validator](/docs/automations/user-group-validator)\\n - [Work duration](/docs/automations/work-duration)\\n -", + "title": "Computer for User Insights | Session analytics | Computer for Your Customers | DevRev" } ] }, @@ -4764,54 +4764,54 @@ "query": "Just-in-time (JIT) provisioning for dynamic access", "retrievals": [ { - "id": "ART-1978_KNOWLEDGE_NODE-41", - "text": "If no such contact is found, JIT provisioning automatically creates a user account, allowing immediate access to the portal. This means users can sign up and log in without manual contact creation within the app.\\n* **Existing contacts without mapped accounts**: If a user is already a contact within the app but does not have a mapped account, they can still log in and create a ticket. In this scenario, the login is performed under the default workspace assigned to the contact.\\n* **Account", + "id": "ART-1978_KNOWLEDGE_NODE-40", + "text": " portion is based on your company name.\\n\\nIf you want to host your customer portal on a custom domain, please contact our support team.\\n\\nJust-in-time access to the customer portal\\n------------------------------------------\\n\\nDevRev offers just-in-time (JIT) provisioning to streamline login processes by automatically handling user account management.\\n\\n* **Automatic account creation**: When a user logs in, the system verifies if the user exists as a contact within an account.", "title": "Customer portal | Computer for Support Teams | DevRev" }, { - "id": "ART-738_KNOWLEDGE_NODE-17", - "text": "level\\n Also, some vendors who didn\\xe2\\x80\\x99t grow up in the \\xe2\\x80\\x9cas a service\\xe2\\x80\\x9d era will need to change processes to embrace CI/CD (some may have)\\n A good ask here is how frequently changes are deployed\\n When something new comes out, we can react and enable rapidly; others may be slower to enable, leading to a gap between when something is \\xe2\\x80\\x9cavailable\\xe2\\x80\\x9d and \\xe2\\x80\\x9creally available\\xe2\\x80\\x9d\\n \\n \\n\\n\\nMost of the available", - "title": "DevRev | Built for AI (not by AI... yet)" + "id": "ART-1978_KNOWLEDGE_NODE-41", + "text": "If no such contact is found, JIT provisioning automatically creates a user account, allowing immediate access to the portal. This means users can sign up and log in without manual contact creation within the app.\\n* **Existing contacts without mapped accounts**: If a user is already a contact within the app but does not have a mapped account, they can still log in and create a ticket. In this scenario, the login is performed under the default workspace assigned to the contact.\\n* **Account", + "title": "Customer portal | Computer for Support Teams | DevRev" }, { - "id": "ART-1978_KNOWLEDGE_NODE-40", - "text": " portion is based on your company name.\\n\\nIf you want to host your customer portal on a custom domain, please contact our support team.\\n\\nJust-in-time access to the customer portal\\n------------------------------------------\\n\\nDevRev offers just-in-time (JIT) provisioning to streamline login processes by automatically handling user account management.\\n\\n* **Automatic account creation**: When a user logs in, the system verifies if the user exists as a contact within an account.", - "title": "Customer portal | Computer for Support Teams | DevRev" + "id": "ART-4022_KNOWLEDGE_NODE-25", + "text": "efficiently handles any number of work items while providing dynamic error handling and detailed tracking. With comprehensive status reporting, users receive a clear breakdown of successful and failed operations, including row numbers, error reasons, and the display IDs of the created/updated work items.\\n\\nFeature\\n-------\\n\\n* **Access Control**: Ensures only authorized users from the group selected in the snap-in configuration can run the snap-in\\n\\nCommands\\n--------\\n\\n*", + "title": "CSV work item uploader | Automate | Snap-ins | DevRev" }, { - "id": "ART-1687_KNOWLEDGE_NODE-3", - "text": "Jira, simplifying the process.\\n2. **Provide credentials:** During development, you\\xe2\\x80\\x99ll provide your developer keyring of type `oauth-secret` which contains client ID and client secret for the chosen service within the keyring definition. These credentials are securely stored and not distributed with your published snap-in.\\n3. **OAuth 2.0 flow:** When your snap-in needs to access user data from the external service, it initiates the OAuth flow. This typically involves redirecting the", - "title": "OAuth 2.0 configuration: Securely storing access tokens | DevRev | Docs" + "id": "ART-16570_KNOWLEDGE_NODE-13", + "text": "and improve, making information access increasingly effortless over time.\\n\\nData-backed transformation\\n--------------------------\\n\\nSince the rollout in June 2025, the data shows clear improvements in operational efficiency:\\n\\n* **+10 hrs saved** every user each week\\n* **~40% faster ticket resolution** when DevRev is used\\n* **Up to 75% faster resolution** in specific cases\\n* **Consistent adoption** across the team through June and July\\n\\nBenefits\\n--------\\n\\nFAME\\'s adoption of", + "title": "FAME transforms information access with AI-powered enterprise search" }, { - "id": "ART-992_KNOWLEDGE_NODE-13", - "text": "delivery model where we can offload the burden of requests from hitting origin and push more to the edge (more to come here!).\\n\\nIn our case we are using a mix of edge compute (C@E) which allows us to compile and execute RUST code on Fastly\\xe2\\x80\\x99s edge, which can also take advantage of their CDN which can cache content from origin.\\n\\nA quick note on WebAssembly (WASM)\\xe2\\x80\\xa6 this is one thing that is very interesting/exciting and will be one of the core enablers to making clients", - "title": "Perimeter security with Fastly edge and AWS \u2014 Part I" + "id": "ART-1641_KNOWLEDGE_NODE-53", + "text": "provisioned and/or issue a Rev session token.\\nShow 9 properties\\nscope string Optional\\nThe requested set of scopes associated with the issued token. A space-delimited list of values in which the order of values does not matter.\\nsubject_token string Optional\\nRepresents the entity that requests the token. Not required when requesting an application access token (AAT).\\nsubject_token_type enum Optional\\nThe type of the subject token.\\nShow 9 enum values\\ntoken_hint string Optional\\nA hint that", + "title": "Get Post \u2014 DevRev | Docs" }, { - "id": "ART-992_KNOWLEDGE_NODE-12", - "text": "0 IN A 151.101.194.137\\n;; Query time: 50 msec\\n;; SERVER: 172.29.208.1#53(172.29.208.1)\\n;; WHEN: Thu Apr 14 09:29:47 CDT 2022\\n;; MSG SIZE rcvd: 168\\n\\n\\nRequest handling/caching\\n\\nTraditionally a lot of delivery models would rely on CDNs only for their static asset caching and DDoS mitigation, still relying on origin to handle the majority of requests.\\n\\nHowever, I do believe with edge compute and the ability to execute logic efficiently on the edge via WASM we will see an inverting of the", - "title": "Perimeter security with Fastly edge and AWS \u2014 Part I" + "id": "ART-1802_KNOWLEDGE_NODE-53", + "text": "provisioned and/or issue a Rev session token.\\nShow 9 properties\\nscope string Optional\\nThe requested set of scopes associated with the issued token. A space-delimited list of values in which the order of values does not matter.\\nsubject_token string Optional\\nRepresents the entity that requests the token. Not required when requesting an application access token (AAT).\\nsubject_token_type enum Optional\\nThe type of the subject token.\\nShow 9 enum values\\ntoken_hint string Optional\\nA hint that", + "title": "Get Post \u2014 DevRev | Docs" }, { - "id": "ART-738_KNOWLEDGE_NODE-13", - "text": "customization in from the start\\n \\n We knew extensibility would be key for any platform\\n Given the simplicity of customization, we can easily extend our object model with new annotations or context that can be used and fed into models\\n This means, that a customer or vendor, can easily extend our object model with new data on objects which can be used by models, new object types, or with the output of a model\\n \\n \\n We built multi-tenancy into the object\\n \\n", - "title": "DevRev | Built for AI (not by AI... yet)" + "id": "ART-1650_KNOWLEDGE_NODE-53", + "text": "provisioned and/or issue a Rev session token.\\nShow 9 properties\\nscope string Optional\\nThe requested set of scopes associated with the issued token. A space-delimited list of values in which the order of values does not matter.\\nsubject_token string Optional\\nRepresents the entity that requests the token. Not required when requesting an application access token (AAT).\\nsubject_token_type enum Optional\\nThe type of the subject token.\\nShow 9 enum values\\ntoken_hint string Optional\\nA hint that", + "title": "List Post \u2014 DevRev | Docs" }, { - "id": "ART-992_KNOWLEDGE_NODE-8", - "text": "any security groups with inbound rules allowing 0.0.0.0/0 with any/all port/protocols, or inbound SSH (yikes) you should consider evaluating things :)\\n\\nFastly CDN/C@E\\n\\n\\n\\nCDNs are not a new concept and have been around for years providing static asset caching and DDoS prevention.\\n\\nHowever, in the past few years, these have expanded to now include capabilities like web-application firewalls (WAFs) and edge compute (logic execution in the CDN) capabilities.\\n\\nIn this section,", - "title": "Perimeter security with Fastly edge and AWS \u2014 Part I" + "id": "ART-1607_KNOWLEDGE_NODE-53", + "text": "provisioned and/or issue a Rev session token.\\nShow 9 properties\\nscope string Optional\\nThe requested set of scopes associated with the issued token. A space-delimited list of values in which the order of values does not matter.\\nsubject_token string Optional\\nRepresents the entity that requests the token. Not required when requesting an application access token (AAT).\\nsubject_token_type enum Optional\\nThe type of the subject token.\\nShow 9 enum values\\ntoken_hint string Optional\\nA hint that", + "title": "Get Post \u2014 DevRev | Docs" }, { - "id": "ART-738_KNOWLEDGE_NODE-14", - "text": "Rather than physically segmenting tenant data, we built tenancy into the objects using specific attributes which act as partitions\\n This allows us to create macro partitions (e.g., customer) or extremely granular partitions (e.g., user level)\\n This gives us a ton of flexibility as all data is in one place and the granularity can range from macro to micro\\n \\n \\n We designed our services for the cloud\\n \\n Being built in the \\xe2\\x80\\x9cera of cloud\\xe2\\x80\\x9d we had a", - "title": "DevRev | Built for AI (not by AI... yet)" + "id": "ART-1835_KNOWLEDGE_NODE-53", + "text": "provisioned and/or issue a Rev session token.\\nShow 9 properties\\nscope string Optional\\nThe requested set of scopes associated with the issued token. A space-delimited list of values in which the order of values does not matter.\\nsubject_token string Optional\\nRepresents the entity that requests the token. Not required when requesting an application access token (AAT).\\nsubject_token_type enum Optional\\nThe type of the subject token.\\nShow 9 enum values\\ntoken_hint string Optional\\nA hint that", + "title": "List \u2014 DevRev | Docs" }, { - "id": "ART-970_KNOWLEDGE_NODE-102", - "text": "groundwork, ensuring we possessed the requisite keys to partition and segment data effectively. This profound understanding of the structure empowered us to fashion granular and precise authorization mechanisms. By dedicating upfront effort to this aspect, we\\xe2\\x80\\x99ve endowed our system with authorization capabilities that some mature companies can only envision, including support for role-based access control (RBAC), attribute-based access control (ABAC), policy-based access control", - "title": "The Story" + "id": "ART-1597_KNOWLEDGE_NODE-53", + "text": "provisioned and/or issue a Rev session token.\\nShow 9 properties\\nscope string Optional\\nThe requested set of scopes associated with the issued token. A space-delimited list of values in which the order of values does not matter.\\nsubject_token string Optional\\nRepresents the entity that requests the token. Not required when requesting an application access token (AAT).\\nsubject_token_type enum Optional\\nThe type of the subject token.\\nShow 9 enum values\\ntoken_hint string Optional\\nA hint that", + "title": "Update \u2014 DevRev | Docs" } ] }, @@ -4820,54 +4820,54 @@ "query": "Audit logging for all customer portal activities", "retrievals": [ { - "id": "ART-1978_KNOWLEDGE_NODE-32", - "text": "on the following URL: support.devrev.ai/.\\n* Your customers can log in on the portal by entering their registered email address and OTP sent to that email address.\\n\\n![]()\\n\\n### Customer roles and permissions\\n\\nThe customer portal has two levels of customer roles and permissions:\\n\\n* **Verified customers**: Customers who can log in on the portal and see the tickets that they have created.\\n* **Customer admins**: Customers who can log in on the portal and see not just their own", - "title": "Customer portal | Computer for Support Teams | DevRev" + "id": "ART-16789_KNOWLEDGE_NODE-34", + "text": "controls, activity logging, and dedicated customer success management for enterprise customers.'", + "title": "Computer General FAQs" }, { - "id": "ART-1978_KNOWLEDGE_NODE-46", - "text": "tracking, and team collaboration](#ticket-creation-tracking-and-team-collaboration)\\n* [Conversations and messaging](#conversations-and-messaging)\\n* [Article search](#article-search)\\n* [SEO compatibility](#seo-compatibility)\\n* [Get started](#get-started)\\n* [Customer roles and permissions](#customer-roles-and-permissions)\\n* [Set up customer admins](#set-up-customer-admins)\\n* [Customer portal login methods](#customer-portal-login-methods)\\n* [Integrating your knowledge base", - "title": "Customer portal | Computer for Support Teams | DevRev" + "id": "ART-15688_KNOWLEDGE_NODE-30", + "text": "and feature requests\\n* **Conversations**: Track time spent on customer conversations and discussions\\n\\n[PreviousDescope identity validation](/docs/automations/descope-identity-validation)[NextHTTP archive file upload & sanitization](/docs/automations/har-sanitization)\\n\\n#### On this page\\n\\n* [Installation](#installation)\\n* [Configuration](#configuration)\\n* [Features](#features)\\n* [How to use](#how-to-use)\\n* [Supported object types](#supported-object-types)\\n\\n[Enterprise grade security", + "title": "Effort logger | Automate | Snap-ins | DevRev" }, { - "id": "ART-1978_KNOWLEDGE_NODE-34", - "text": "registered email address and go to **Settings** > **User management** > **Groups > Customer Admins**.\\n2. Select the **Add User** option in the top-right corner to search for the customer whom you want to designate as a customer admin.\\n\\n### Customer portal login methods\\n\\nThe customer portal supports three login methods:\\n\\n1. Email OTP (One-Time Password): User enters their email, receives a one-time code, and enters it to log in.\\n2. SSO: Users log in through organization\\xe2\\x80\\x99s", + "id": "ART-1978_KNOWLEDGE_NODE-32", + "text": "on the following URL: support.devrev.ai/.\\n* Your customers can log in on the portal by entering their registered email address and OTP sent to that email address.\\n\\n![]()\\n\\n### Customer roles and permissions\\n\\nThe customer portal has two levels of customer roles and permissions:\\n\\n* **Verified customers**: Customers who can log in on the portal and see the tickets that they have created.\\n* **Customer admins**: Customers who can log in on the portal and see not just their own", "title": "Customer portal | Computer for Support Teams | DevRev" }, { - "id": "ART-1978_KNOWLEDGE_NODE-24", - "text": "creation, tracking, and team collaboration](#ticket-creation-tracking-and-team-collaboration)\\n* [Conversations and messaging](#conversations-and-messaging)\\n* [Article search](#article-search)\\n* [SEO compatibility](#seo-compatibility)\\n* [Get started](#get-started)\\n* [Customer roles and permissions](#customer-roles-and-permissions)\\n* [Set up customer admins](#set-up-customer-admins)\\n* [Customer portal login methods](#customer-portal-login-methods)\\n* [Integrating your knowledge base", - "title": "Customer portal | Computer for Support Teams | DevRev" + "id": "ART-2050_KNOWLEDGE_NODE-27", + "text": "[methods](https://developer.devrev.ai/public/sdks/web/methods) providing the framework for customer support interactions.\\n\\n### \\xf0\\x9f\\x8e\\x9e\\xef\\xb8\\x8f Session recording and analytics\\n\\n[Session analytics](/docs/plug/session-analytics-intro) captures user website interactions through recordings and detailed logging, enabling businesses to visualize behavior patterns, analyze conversion funnels, and optimize user experience through Computer for User Insights.\\n\\n### \\xf0\\x9f\\x93\\x9d", + "title": "Computer for Your Customers | DevRev" }, { - "id": "ART-16789_KNOWLEDGE_NODE-34", - "text": "controls, activity logging, and dedicated customer success management for enterprise customers.'", - "title": "Computer General FAQs" + "id": "ART-15716_KNOWLEDGE_NODE-23", + "text": "steps, your customer portal will be accessible at the custom domain you\\'ve chosen.Account and Authentication\\n\\nTroubleshooting Sign-Up Issues\\n\\nIf a user can\\xe2\\x80\\x99t sign up:\\n\\nConfirm which signup method they\\xe2\\x80\\x99re using (email, SSO, etc.).\\n\\nCheck if they\\xe2\\x80\\x99re seeing an error message\\xe2\\x80\\x94if so, note the exact wording.\\n\\nCommon blockers include: email already in use, password policy issues, or incomplete form fields.\\n\\nIf the issue persists after retrying,", + "title": "Support queries related playbook" }, { - "id": "ART-2664_KNOWLEDGE_NODE-27", - "text": "your\\n [website](https://developer.devrev.ai/sdks/web/installation) or\\n [mobile app](https://developer.devrev.ai/sdks/mobile).\\n2. For web applications, configure\\n [user identification](https://developer.devrev.ai/sdks/web/user-identity).\\n3. Enable session recording for your users, go to **Settings** > **PluG and Portal** >\\n **Session Replays** and enable recording for your desired platform.\\n\\n **Note**: Alternatively, you can enable session recording during Plug SDK\\n", - "title": "Session analytics | Computer for Your Customers | DevRev" + "id": "ART-1978_KNOWLEDGE_NODE-40", + "text": " portion is based on your company name.\\n\\nIf you want to host your customer portal on a custom domain, please contact our support team.\\n\\nJust-in-time access to the customer portal\\n------------------------------------------\\n\\nDevRev offers just-in-time (JIT) provisioning to streamline login processes by automatically handling user account management.\\n\\n* **Automatic account creation**: When a user logs in, the system verifies if the user exists as a contact within an account.", + "title": "Customer portal | Computer for Support Teams | DevRev" }, { - "id": "ART-2665_KNOWLEDGE_NODE-1", - "text": "[Apps](/docs/product/apps)\\n + [Groups](/docs/product/groups)\\n + [Parts & trails](/docs/product/parts)\\n + [Vistas](/docs/product/vistas)\\n\\n - [Vista Reports](/docs/product/vista-reports)\\n - [Board view](/docs/product/board-view)\\n + [Tasks](/docs/product/tasks)\\n + [Updates](/docs/product/updates)\\n + [Customer email notifications](/docs/product/customer-emails)\\n + [Roles](/docs/product/roles)\\n\\n - [Default privileges by group](/docs/product/privs)\\n + [Access", + "id": "ART-2665_KNOWLEDGE_NODE-36", + "text": "Insights](/docs/plug/observability)[NextCross-domain session tracking](/docs/plug/cross-domain-session)\\n\\n#### On this page\\n\\n[Enterprise grade security to protect customer data\\n\\nLearn more about it.\\n\\n![]()](/blog/soc-compliance)\\n\\nComputer\\n\\n* [Meet Computer](/meet-computer)\\n* [How Computer works](/how-computer-works)\\n\\nApps\\n\\n* [For Support Teams](/for-support-teams)\\n* [For Builders](/for-builders)\\n* [For Customers](/for-customers)\\n* [For User Insights](/for-user-insights)\\n*", "title": "Session recording options | Session analytics | Computer for Your Customers | DevRev" }, { - "id": "ART-1978_KNOWLEDGE_NODE-25", - "text": "articles](#integrating-your-knowledge-base-articles)\\n* [Customize the customer portal](#customize-the-customer-portal)\\n* [Customize portal URL](#customize-portal-url)\\n* [Just-in-time access to the customer portal](#justintime-access-to-the-customer-portal)\\n* [Troubleshooting](#troubleshooting)\\n\\n1. [Documentation](/docs)\\n3. [Computer for Support Teams](/docs/product/support)\\n[Customer portal](/docs/product/support-portal)\\n\\nCustomer portal\\n===============\\n\\nThe customer portal is an", + "id": "ART-1978_KNOWLEDGE_NODE-27", + "text": "portal\\n-------------------------------------\\n\\n* **Enhanced customer experience**: Customers can access self-service options, track their tickets, and receive timely updates, leading to improved satisfaction.\\n* **Efficient ticket management**: The portal streamlines the ticket creation, assignment, and tracking process, ensuring faster resolution times.\\n* **Seamless, timely, and transparent communication**: Customers and support teams can engage in threaded conversations within the portal,", "title": "Customer portal | Computer for Support Teams | DevRev" }, { - "id": "ART-2664_KNOWLEDGE_NODE-1", - "text": "[Groups](/docs/product/groups)\\n + [Parts & trails](/docs/product/parts)\\n + [Vistas](/docs/product/vistas)\\n\\n - [Vista Reports](/docs/product/vista-reports)\\n - [Board view](/docs/product/board-view)\\n + [Tasks](/docs/product/tasks)\\n + [Updates](/docs/product/updates)\\n + [Customer email notifications](/docs/product/customer-emails)\\n + [Roles](/docs/product/roles)\\n\\n - [Default privileges by group](/docs/product/privs)\\n + [Access control](/docs/product/access-control)\\n +", - "title": "Session analytics | Computer for Your Customers | DevRev" + "id": "ART-13178_KNOWLEDGE_NODE-65", + "text": "potentially perpetuating unfair treatment across customer groups.\\n\\n**Solution:** Develop comprehensive bias detection frameworks and conduct regular audits across agent functions to identify and correct problematic patterns.\\n\\n### Accountability questions\\n\\n**Challenge:** Autonomous decision-making creates uncertainty about responsibility when systems make problematic choices.\\n\\n**Solution:** Establish clear accountability structures defining human oversight responsibilities and explicit", + "title": "Understanding Agentic AI: Capabilities and Implications for the Future" }, { - "id": "ART-1978_KNOWLEDGE_NODE-1", - "text": "[Groups](/docs/product/groups)\\n + [Parts & trails](/docs/product/parts)\\n + [Vistas](/docs/product/vistas)\\n\\n - [Vista Reports](/docs/product/vista-reports)\\n - [Board view](/docs/product/board-view)\\n + [Tasks](/docs/product/tasks)\\n + [Updates](/docs/product/updates)\\n + [Customer email notifications](/docs/product/customer-emails)\\n + [Roles](/docs/product/roles)\\n\\n - [Default privileges by group](/docs/product/privs)\\n + [Access control](/docs/product/access-control)\\n +", - "title": "Customer portal | Computer for Support Teams | DevRev" + "id": "ART-15688_KNOWLEDGE_NODE-29", + "text": "system automatically validates:\\n\\n * Date format and range (within last 10 days to next 10 days)\\n * Hours and minutes values\\n * Prevents logging when both hours and minutes are zero\\n3. **Confirmation**: After successful validation, the effort is logged and a confirmation message appears in the timeline.\\n\\nSupported object types\\n----------------------\\n\\nThe Effort logger snap-in works with the following object types:\\n\\n* **Tickets**: Log effort against support tickets, bug reports,", + "title": "Effort logger | Automate | Snap-ins | DevRev" } ] }, @@ -4881,49 +4881,49 @@ "title": "Plug widget customization | Computer for Your Customers | DevRev" }, { - "id": "ART-3109_KNOWLEDGE_NODE-28", - "text": "highlight something to your users.\\n\\n#### **Turing search**\\n\\nHere's how Turing search works in Plug.\\n\\n![]()\\n\\nSpotlight cards\\n---------------\\n\\nSpotlight cards are top-level cards on the Plug widget. You can use them for showcasing PR articles, product releases, blog posts, or any other marketing/product-related content that can educate your users about things happening in your company.\\n\\nHere is how a spotlight card looks.\\n\\n![]()\\n\\n### Add a spotlight card\\n\\n1. In the DevRev app,", - "title": "Plug widget customization | Computer for Your Customers | DevRev" + "id": "ART-1846_KNOWLEDGE_NODE-12", + "text": "snap-in configuration.\\n\\n**Note: This endpoint is currently in beta and may be subject to change in the future. Reach out to us via Plug to subscribe to changes to beta endpoints.**\\n\\n### Request payload\\n\\nThe request payload should be a JSON object with the following properties:\\n\\n* `id` (string, required): The ID of the snap-in to update.\\n* `inputs_values` (object, required): An object containing the input values to update. The properties of this object should match the input names", + "title": "Customizing snap-in configuration | DevRev | Docs" }, { - "id": "ART-3109_KNOWLEDGE_NODE-27", - "text": "shown at the top of your widget.\\n* Search: Enables users to search for articles through the widget.\\n* Search bar title: The text shown in the search bar.\\n\\n* [Turing search](#turing-search): Computer answers search queries of the users.\\n* Open articles in Plug: Open your linked articles within the Plug Widget.\\n* Recent conversations: Show recent conversations card on Plug Home.\\n* Recent tickets: Show recent tickets card on Plug Home.\\n* Add a Card: Create a Spotlight card to announce or", - "title": "Plug widget customization | Computer for Your Customers | DevRev" + "id": "ART-1847_KNOWLEDGE_NODE-15", + "text": "snap-in configuration.\\n\\n**Note: This endpoint is currently in beta and may be subject to change in the future. Reach out to us via PLuG to subscribe to changes to beta endpoints.**\\n\\n### Request payload\\n\\nThe request payload should be a JSON object with the following properties:\\n\\n * `id` (string, required): The ID of the snap-in to update.\\n * `inputs_values` (object, required): An object containing the input values to update. The properties of this object should match the input names", + "title": "Customizing snap-in configuration \u2014 DevRev | Docs" }, { - "id": "ART-3109_KNOWLEDGE_NODE-24", - "text": "[Product demos](/docs/DevRevU/demos)\\n\\nOn this page\\n\\n* [Configuration](#configuration)\\n* [Styling](#styling)\\n* [Layout](#layout)\\n* [\\\\*\\\\*Turing search\\\\*\\\\*](#turing-search)\\n* [Spotlight cards](#spotlight-cards)\\n* [Add a spotlight card](#add-a-spotlight-card)\\n\\n1. [Documentation](/docs)\\n3. [Computer for Your Customers](/docs/plug)\\n[Plug widget customization](/docs/plug/customize)\\n\\nPlug widget customization\\n=========================\\n\\nYou can customize the look and feel of your", - "title": "Plug widget customization | Computer for Your Customers | DevRev" + "id": "ART-1304_KNOWLEDGE_NODE-25", + "text": "information.\\nRequest.\\n\\nThis endpoint expects an object.\\nid string Required\\nThe ID of account to update.\\nartifacts object Optional\\nShow property\\ncustom_fields map from strings to any Optional\\nApplication-defined custom fields.\\ndescription string Optional\\nUpdated description of the account.\\ndisplay_name string Optional\\nUpdated display name for the account.\\ndomains list of strings Optional\\nUpdated list of company\\'s domain names. Example - [\\'devrev.ai\\'].\\nexternal_refs list of", + "title": "Get \u2014 DevRev | Docs" }, { - "id": "ART-10697_KNOWLEDGE_NODE-31", - "text": "boosting engagement and reducing repetitive inquiries. To enable Plug, go to **Settings > Portal Settings**, activate Plug widget, and **Save** and **Publish**.\\n\\n![]()\\xc2\\xa0For more information about *Support App*, refer to the following articles: \\xe2\\x80\\xa3 [Support snap-ins | Support](/docs/product/snapins-support) \\xe2\\x80\\xa3 [Support best practices | Support](/docs/product/support-bp) \\xe2\\x80\\xa3 [Support](/docs/product/support) \\xe2\\x80\\xa3", - "title": "February 2025 | Changelog | DevRev" + "id": "ART-2035_KNOWLEDGE_NODE-59", + "text": "customization will be shown.\\n* Summary cards are static Slack messages and may not reflect real-time data.\\n + Use the **Refresh** button at the bottom of the card to update.\\n + A timestamp indicates the last update time.\\n* To view all fields or update the object, click the **View/Update** button.\\n\\nThe information shown in the summary card differs by channel:\\n\\n* In **Internal channels**, all summary fields are shown.\\n* In an **External channels**, summary fields are", + "title": "Slack | Integrate | Snap-ins | DevRev" }, { - "id": "ART-1360_KNOWLEDGE_NODE-1", - "text": "application/json\" \\\\ |\\n| > | -d \\'{}\\' |\\n```\\n\\n[Try it](/api-reference/parts/update?explorer=true)\\n\\n200Successful\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | { |\\n| 2 | \"part\": { |\\n| 3 | \"created_by\": { |\\n| 4 | \"display_id\": \"string\", |\\n| 5 | \"id\": \"string\", |\\n| 6 | \"display_name\": \"string\", |\\n| 7 | \"display_picture\": { |\\n| 8 | \"display_id\": \"string\", |\\n| 9 | \"id\": \"string\", |\\n| 10 | \"file\": { |\\n| 11 | \"type\": \"string\", |\\n| 12 | \"name\": \"string\", |\\n| 13 | \"size\": 1 |\\n| 14 | } |\\n| 15", - "title": "Update Part | DevRev | Docs" + "id": "ART-15506_KNOWLEDGE_NODE-26", + "text": "relevant user information. Plug can only be initialized once per page load.\\n\\nIn most cases, this works as expected\\xe2\\x80\\x94user identification typically happens after login or signup, which causes a page reload and clears any previous Plug instance.\\n\\nHowever, if your application needs to update the user identity without a full page refresh, you need to explicitly delete the existing Plug instance before initializing it again with the new user information.\\n\\n```\\n| | |\\n| --- | ---", + "title": "Identify your users with Plug | DevRev | Docs" }, { - "id": "ART-1290_KNOWLEDGE_NODE-17", - "text": "[Card](/snapin-development/references/snapkit#card) snap.\\n\\n![]()\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | { |\\n| 2 | \"elements\": [ |\\n| 3 | { |\\n| 4 | \"direction\": \"row\", |\\n| 5 | \"elements\": [ |\\n| 6 | { |\\n| 7 | \"action_id\": \"PRIMARY\", |\\n| 8 | \"action_type\": \"remote\", |\\n| 9 | \"style\": \"primary\", |\\n| 10 | \"text\": { |\\n| 11 | \"text\": \"PRIMARY\", |\\n| 12 | \"type\": \"plain_text\" |\\n| 13 | }, |\\n| 14 | \"type\": \"button\", |\\n| 15 | \"value\": \"PRIMARY\" |\\n| 16 | }, |\\n| 17 | { |\\n| 18 | \"action_id\":", - "title": "Snapkit | DevRev | Docs" + "id": "ART-1846_KNOWLEDGE_NODE-18", + "text": "`updateSnapInInputs` function to make the POST request to the `snap-ins.update` endpoint.\\n\\nIf the request is successful, it returns a success response with a status code of 200 and a message indicating that the snap-in was updated successfully.\\n\\nIf an error occurs, it catches the error and returns an error response with an appropriate status code and an error message containing the error details.\\n\\n##### \\n\\nNote: This endpoint is currently in beta, and its functionality or parameters may", + "title": "Customizing snap-in configuration | DevRev | Docs" }, { - "id": "ART-2897_KNOWLEDGE_NODE-24", - "text": "\"Credit Card\", \\n 6| \"expiry_date\" : \"2024-12-12\" \\n 7| } \\n 8| window.plugSDK.trackEvent(\"signed_up\",properties)\\n[/code] \\n \\nTo learn more about tracking events, visit [Track events](/public/sdks/web/track-events).\\n\\n## Restart session recording\\n\\nThe `restartSessionRecording` method is used to restart session recording.\\n\\n[code]\\n\\n 1| window.plugSDK.restartSessionRecording(); \\n ---|---\\n[/code] \\n \\nWas this page helpful?YesNo\\n\\n[Custom implementationUp", - "title": "Methods \u2014 DevRev | Docs" + "id": "ART-1296_KNOWLEDGE_NODE-6", + "text": "Component | Compatibility check |\\n| --- | --- |\\n| Keyrings | For existing keyrings: - The description can be changed. - The display name can be changed. - New values for allowed types under that connection could be added, but existing allowed types can\\xe2\\x80\\x99t be removed. Any existing connection can be removed A new connection can\\xe2\\x80\\x99t be added. |\\n| Event sources | For existing event sources: - The description can be changed. - The display name can be changed.", + "title": "Upgrade snap-ins | DevRev | Docs" }, { - "id": "ART-15496_KNOWLEDGE_NODE-1", - "text": "SDK](/sdks/web/installation)\\n\\nCustom implementation\\n=====================\\n\\nCopy page\\n\\nPlug has a completely [no-code way](https://docs.devrev.ai/plug/customize#branding-style-and-layout) of changing the look and interaction of your widget. In case you wish to make your Plug widget more interactive and customized to how your app is structured, you can use these customization properties to set up your widget.\\n\\n##### \\n\\nIf you have customized these properties of the widget through the", - "title": "Custom implementation | DevRev | Docs" + "id": "ART-4063_KNOWLEDGE_NODE-2", + "text": "documented endpoint is for exposition and not provided by DevRev.\\n\\n### Request\\n\\nThis endpoint expects an object.\\n\\nidstringRequired`format: \"id\"`\\n\\nThe event\\xe2\\x80\\x99s ID.\\n\\nwebhook_idstringRequired`format: \"id\"`\\n\\nID of the webhook for the event.\\n\\ntypeenumOptional\\n\\nThe event types that the webhook will receive.\\n\\nShow 70 enum values\\n\\naccount_createdobjectOptional\\n\\nShow property\\n\\naccount_deletedobjectOptional\\n\\nShow 2 properties\\n\\naccount_updatedobjectOptional\\n\\nShow 2", + "title": "Event Webhooks \u2014 DevRev | Docs" }, { - "id": "ART-15506_KNOWLEDGE_NODE-25", - "text": "8 | }) |\\n```\\n\\n##### \\n\\nNote that the `updateIdentity` method cannot be used to update the `user_ref` of the user. In order to change the identity of the user completely to a new one, you need to re-initialize Plug. See the [Changing the user identity](/sdks/web/user-identity#changing-the-user-identity) section for more details.\\n\\nChanging the user identity\\n--------------------------\\n\\nAs described in the above sections, to identify a user, you need to initialize the Plug SDK with the", - "title": "Identify your users with Plug | DevRev | Docs" + "id": "ART-1588_KNOWLEDGE_NODE-392", + "text": "an object.\\nsnap_in_version object\\nShow 2 properties\\nevent_sources map from strings to strings Optional\\nThe event sources for the snap-in.\\ninputs map from strings to any Optional\\nThe inputs for the snap-in.\\nkeyrings map from strings to objects Optional\\nMap of keyring names and its data.\\nShow 2 properties\\nAPI Reference snap-ins Update.\\n\\nPOST https:// api.devrev.ai / snap-ins.update\\nUpdates a snap-in.\\nRequest.\\n\\nThis endpoint expects an object.\\nid string Required\\nThe ID of the", + "title": "Get \u2014 DevRev | Docs" } ] }, @@ -4932,54 +4932,54 @@ "query": "ticket resolution time close to breach after ticket resolved", "retrievals": [ { - "id": "ART-1979_KNOWLEDGE_NODE-48", - "text": "engineer can directly close and cancel such tickets.\\n* *Accepted* (A)\\n\\n The ticket requires a new feature development on the platform for resolution. However, there is no active work on the ticket but the feature addition required to meet the ticket will be done in the future. This stage is added to ensure that feature requests do not linger in the APA queue and to ensure that the right features are prioritized during roadmap planning.\\n* *Resolved* (R)\\n\\n The goal target stage for", - "title": "Tickets | Computer for Support Teams | DevRev" + "id": "ART-2017_KNOWLEDGE_NODE-25", + "text": "ticket\\'s owner and subscribers, when a ticket\\'s resolution time SLA changes into the *Warning* or *Breached* stage.\\n\\n![]()\\n\\nFor more information, refer to the\\n[SLA status change Slack notifier snap-in](/marketplace/sla-status-change-slack-notifier) on the DevRev\\nmarketplace.\\n\\nInstallation\\n------------\\n\\n1. Create a Slack app for your workspace in .\\n2. In App features, generate bot token in **OAuth & Permissions**.\\n3. Grant the app bot the following", + "title": "SLA status change Slack notifier | Automate | Snap-ins | DevRev" }, { - "id": "ART-1979_KNOWLEDGE_NODE-47", - "text": "validate the fix with the user and then to *resolved*. If the user wants to cancel the ticket then the stage moves to *canceled*.\\n\\n**Closed**\\n\\n* *Canceled* (C)\\n\\n The ticket is determined to be invalid either by the user or the customer experience engineer. In certain scenarios, a ticket may have been created by accident and may be canceled by the creator. In other scenarios, garbage tickets may be created through automation or because of spam. Automation or the customer experience", - "title": "Tickets | Computer for Support Teams | DevRev" + "id": "ART-1004_KNOWLEDGE_NODE-7", + "text": "time it takes for a specific support engineer to resolve a customer issue from the moment it\\xe2\\x80\\x99s reported.\\n \\n \\n Calculation\\n \\n (Sum of resolution times for all resolved tickets by the engineer) / (Total number of resolved tickets by the engineer)\\n \\n \\n\\n\\nSELECT engineer_id, AVG(TIMESTAMPDIFF(MINUTE, t.created_at, t.resolved_at)) AS IndividualAverageResolutionTime\\nFROM tickets t\\nWHERE t.status = 'resolved'\\nAND EXTRACT(@period FROM t.created_at) =", + "title": "Understanding a Support Engineer's Pain Points and KPIs" }, { "id": "ART-1986_KNOWLEDGE_NODE-43", - "text": "tickets that have been in breach for more than one hour.\\n + **Over a day**: Filters all tickets that have been in breach for more than one day.\\n + **Custom**: Filters all tickets that have been in breach from a given date.\\n* **Will breach in**:\\n\\n + **Any**: Filters all tickets that are currently not in breach.\\n + **Over an hour**: Filters all tickets that have less than 1 hour left for breach.\\n + **Over a day**: Filters all tickets that have less than 1 day left for breach.\\n +", + "text": "tickets that have been in breach for more than one hour.\\n + **Over a day**: Filters all tickets that have been in breach for more than one day.\\n + **Custom**: Filters all tickets that have been in breach from a given date.\\n* **Will breach in**:\\n\\n + **Any**: Filters all tickets that are currently not in breach.\\n + **Over an hour**: Filters all tickets that have less than 1 hour left for breach.\\n + **Over a day**: Filters all tickets that have less than 1 day left for breach.\\n +", "title": "Service-level agreement | Computer for Support Teams | DevRev" }, { - "id": "ART-1979_KNOWLEDGE_NODE-41", - "text": "progress\\n\\n\\n\\nOpen\\n\\n\\n\\nEscalate\\n\\n\\n\\nValidate the fix\\n\\n\\n\\nAdditional detail needed\\n\\n\\n\\nCustomer responds\\n\\n\\n\\nStart\\n\\n\\n\\nFeature request accepted\\n\\n\\n\\nResolved\\n\\n\\n\\nNot valid\\n\\n\\n\\nQueued\\n\\n\\n\\nWork in progress\\n\\n\\n\\nAwaiting product assist\\n\\n\\n\\nAwaiting development\\n\\n\\n\\nAwating customer response\\n\\n\\n\\nIn development\\n\\n\\n\\nAccepted\\n\\n\\n\\nResolved\\n\\n\\n\\nCanceled\\n```\\n\\n**Open**\\n\\n* *Queued* (Q)\\n The initial stage for all tickets. When a new ticket is created,", - "title": "Tickets | Computer for Support Teams | DevRev" + "id": "ART-1986_KNOWLEDGE_NODE-41", + "text": "resolution is due in one day, the vista displays five minutes. In the case where the first response isn't provided within five minutes, the timer displays negative values (such as -10m), which indicates that it's been 10 minutes since the first response was due. Conversations or tickets can also be grouped by SLA stages.\\n\\nIn the **Detailed View**, all metrics applied to the ticket or conversation can be viewed along with their current stage.\\n\\nFiltering tickets by Next SLA", + "title": "Service-level agreement | Computer for Support Teams | DevRev" }, { - "id": "ART-2012_KNOWLEDGE_NODE-24", - "text": "customer comments on permanently closed tickets. It allows you to configure the time after which a ticket stage should be marked as closed and creates a new follow-up ticket along with all the attachments and a custom message to let the customers know that the ticket is permanently closed automatically if required.\\n\\nFor more information, refer to the [Follow-up ticket snap-in](https://marketplace.devrev.ai/followup?) on the DevRev marketplace.\\n\\nLet\\xe2\\x80\\x99s say your ticket has the", - "title": "Follow-up ticket | Automate | Snap-ins | DevRev" + "id": "ART-1970_KNOWLEDGE_NODE-26", + "text": "Conversations with SLA breaches with breach type for ticket owners.\\n* **SLA breaches w.r.t. Customer Tier**\\n\\n Number of Conversations with SLA breaches per owner.\\n* **Average Resolution Time**\\n\\n Indicates the average time taken to resolve requests for each conversation owner.\\n\\n[PreviousConversation-SLA Analytics](/docs/dashboards/conversation-sla-analytics)[NextTicket insights](/docs/dashboards/ticket-insights)\\n\\n[Enterprise grade security to protect customer data\\n\\nLearn more about", + "title": "Conversation-Team Performance | Support analytics | Computer for Support Teams | DevRev" }, { - "id": "ART-1986_KNOWLEDGE_NODE-41", - "text": "resolution is due in one day, the vista displays five minutes. In the case where the first response isn't provided within five minutes, the timer displays negative values (such as -10m), which indicates that it's been 10 minutes since the first response was due. Conversations or tickets can also be grouped by SLA stages.\\n\\nIn the **Detailed View**, all metrics applied to the ticket or conversation can be viewed along with their current stage.\\n\\nFiltering tickets by Next SLA", + "id": "ART-1986_KNOWLEDGE_NODE-37", + "text": "a customer * The ticket was created by a customer experience engineer but reported by a customer | A new comment on the ticket by the customer after the customer experience engineer replied | * The agent added a comment to the customer chat * The ticket is moved to Awaiting Customer Response, or the ticket is closed | | |\\n| Full resolution time | * Ticket created by a customer * The ticket was created by a customer experience engineer but reported by a customer | Ticket created | The", "title": "Service-level agreement | Computer for Support Teams | DevRev" }, { - "id": "ART-1981_KNOWLEDGE_NODE-32", - "text": "assigned; tickets should be assigned only to revenue team members.\\n\\nManage tickets\\n--------------\\n\\n* Regularly follow up with the customer on any ticket in the *awaiting customer* stage. If no response is forthcoming in a reasonable amount of time as defined by your SLA, mark the ticket as *resolved*.\\n* Critically assess the severity of the ticket according to the impact on the customer\\xe2\\x80\\x99s business. Blockers are those tickets that are critical to customer adoption or operations.", - "title": "Support best practices | Computer for Support Teams | DevRev" + "id": "ART-1035_KNOWLEDGE_NODE-0", + "text": "b'Goodmeetings uses PLuG to reduce ticket resolution time\\n\\n* Computer\\n* Resources\\n* [Our Customers](/case-study)\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](/request-a-demo)\\n\\nComputer\\n\\nResources\\n\\n[Our Customers](/case-study)\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](/request-a-demo)\\n\\n- [Case Studies](/case-study)\\n\\n- Goodmeetings\\n\\nGoodmeetings uses DevRev to reduce ticket resolution time\\n=========================================================\\n\\n3 min", + "title": "Goodmeetings uses PLuG to reduce ticket resolution time" }, { - "id": "ART-1986_KNOWLEDGE_NODE-36", - "text": "conversations:\\n\\n**Tickets**\\n\\n| Metric | Default conditions | Start event | End event | Pause event | Resume event |\\n| --- | --- | --- | --- | --- | --- |\\n| First response time | * Ticket created by a customer * The ticket was created by a customer experience engineer but reported by a customer | Ticket created | * The agent added a comment to the customer chat * The ticket is moved to Awaiting Customer Response, or the ticket is closed | | |\\n| Next response time | * Ticket created by", - "title": "Service-level agreement | Computer for Support Teams | DevRev" + "id": "ART-4965_KNOWLEDGE_NODE-26", + "text": "snap-in.\\n\\nConfiguration\\n-------------\\n\\nIn the **Configuration Settings**, select the number of days (0 < x < 365) after which a closed ticket becomes immutable.\\n\\n[PreviousTicket issue field migrator](/docs/automations/ticket-issue-field-migrator)[NextTicket email notifier](/docs/automations/ticket-email-notifier)\\n\\n#### On this page\\n\\n* [Installation](#installation)\\n* [Configuration](#configuration)\\n\\n[Enterprise grade security to protect customer data\\n\\nLearn more about", + "title": "Ticket Immutability | Automate | Snap-ins | DevRev" }, { - "id": "ART-1986_KNOWLEDGE_NODE-38", - "text": "ticket is moved to the Closed state | The ticket was moved to Awaiting Customer Response state | The ticket moves to any state except Closed |\\n\\n**Conversations**\\n\\n| Metric | Default conditions | Start event | End event | Pause event | Resume event |\\n| --- | --- | --- | --- | --- | --- |\\n| First response time | The first message sent by a customer | Conversation created | * The agent replied to the conversation * The conversation is moved to Waiting on User/Resolved * The conversation is", - "title": "Service-level agreement | Computer for Support Teams | DevRev" + "id": "ART-1972_KNOWLEDGE_NODE-25", + "text": "SLA breaches**\\n\\n Number of Active Tickets that breached an SLA.\\n* **Tickets with SLA warning**\\n\\n Number of Active Tickets that about to breach an SLA.\\n* **Resolution compliance rate**\\n\\n Percentage of tickets where Resolution SLA was met out of all tickets where Resolution SLA is applied.\\n* **First Response compliance rate**\\n\\n Percentage of tickets where First Response SLA was met out of all tickets where First Response SLA is applied.\\n* **Next Response compliance rate**\\n\\n", + "title": "Ticket-SLA Analytics | Support analytics | Computer for Support Teams | DevRev" }, { - "id": "ART-1975_KNOWLEDGE_NODE-25", - "text": "insights\\n===============\\n\\n* **Tickets created**\\n\\n The number of tickets created within the date range that meet the other filtering criteria.\\n* **Active tickets**\\n\\n The number of tickets that are in the Open or In Progress state.\\n* **Closed tickets**\\n\\n The number of tickets closed within the date range that meet the other filtering criteria.\\n* **Average resolution time**\\n\\n The average time taken to resolve tickets.\\n* **Median resolution time**\\n\\n The median time taken to", - "title": "Ticket insights | Support analytics | Computer for Support Teams | DevRev" + "id": "ART-1977_KNOWLEDGE_NODE-26", + "text": "owner.\\n* **Average Resolution Time**\\n\\n Average time taken to resolve tickets by ticket owners.\\n\\n[PreviousTicket-SLA Analytics](/docs/dashboards/ticket-sla-analytics)[NextConversations](/docs/product/conversation)\\n\\n[Enterprise grade security to protect customer data\\n\\nLearn more about it.\\n\\n![]()](/blog/soc-compliance)\\n\\nComputer\\n\\n* [Meet Computer](/meet-computer)\\n* [How Computer works](/how-computer-works)\\n\\nApps\\n\\n* [For Support Teams](/for-support-teams)\\n* [For", + "title": "Ticket-Team Performance | Support analytics | Computer for Support Teams | DevRev" } ] }, @@ -4987,54 +4987,54 @@ "query_id": "b580c85d-067a-47f0-951d-58b0360254a1", "query": "link single contact to multiple accounts using csv import", "retrievals": [ - { - "id": "ART-2575_KNOWLEDGE_NODE-26", - "text": "the sample CSV.\\n\\n ![]()\\n\\n Columns with headers that do not conform to the predefined schema will not be imported.\\n4. In the dialog box, upload the populated CSV file.\\n5. (Optional) Configure import settings.\\n\\n * **Add tags to identify new imports**: Attach any existing tags to new imports for easy identification post-import.\\n * **Update existing accounts**: Select to update existing accounts by appending new values, rather than creating new objects.\\n6. Click **Import** to", - "title": "Account and contact import | Computer for Growth Teams | DevRev" - }, { "id": "ART-2575_KNOWLEDGE_NODE-25", "text": "contact import\\n==========================\\n\\nYou can upload and manage accounts and contacts by importing data from CSV files.\\n\\n![]()\\n\\nImport data\\n-----------\\n\\n1. Go to the top-right corner of the **Accounts and Contacts** vista and click the \\xe2\\x9a\\xa1 button.\\n2. Click **Download sample CSV**. The sample CSV file includes all the necessary headers and sample values supported by DevRev.\\n3. Open the downloaded sample CSV file. Fill in the required headers and values as specified in", "title": "Account and contact import | Computer for Growth Teams | DevRev" }, { - "id": "ART-2575_KNOWLEDGE_NODE-30", - "text": "CSV import feature currently supports a maximum of 500 rows per request. For larger datasets, split the CSV into smaller files containing up to 500 rows each.\\n\\nTroubleshooting\\n---------------\\n\\nThe following table describes the errors you may encounter during import and how to troubleshoot them:\\n\\n| Error | Resolution |\\n| --- | --- |\\n| Invalid format for phone numbers | Validate the phone number is in E164 Format. For example, +12014631690. |\\n| Tags not found in organization |", + "id": "ART-2575_KNOWLEDGE_NODE-27", + "text": "initiate the process. Notifications about successful imports and any errors will appear in the form of toasts at the bottom left.\\n\\nCSV file requirements\\n---------------------\\n\\n### Mandatory fields\\n\\nTo ensure a successful import, certain fields are required.\\n\\n**Accounts**:\\n\\n* display\\\\_name\\n* external\\\\_refs (a unique identifier for the account, such as the company\\'s website domain.)\\n\\n**Contacts:**\\n\\n* display\\\\_name\\n* external\\\\_ref (a unique identifier for the contact, such as", "title": "Account and contact import | Computer for Growth Teams | DevRev" }, { - "id": "ART-2575_KNOWLEDGE_NODE-28", - "text": "a database identifier or an email address.)\\n* account\\\\_external\\\\_reference (the external reference of the contact\\'s parent account)\\n\\n### Array fields\\n\\nFor fields that accept multiple values, such as **owners** and **industry**, values should be separated by commas (,). For example, Agriculture and Forestry should be written as Agriculture,Forestry.\\n\\n![]()\\n\\nIf a value contains a comma, enclose it in backticks. For example, enter \"Rail, Bus & Taxi\" as `Rail, Bus & Taxi`.\\n\\n###", - "title": "Account and contact import | Computer for Growth Teams | DevRev" + "id": "ART-6175_KNOWLEDGE_NODE-26", + "text": "contacts.\\n* **Link Account and Contact:**\\n Enable this option to link the account and contact to the custom object.\\n* **Account Description Fields:**\\n Enable this option to generate a rich description for accounts using values from multiple Airtable columns.\\n* **Contact Description Fields:**\\n Enable this option to generate a rich description for contacts using values from multiple Airtable columns.\\n* **Airtable Email Columns:**\\n Comma-separated list of names of the columns in", + "title": "Airtable | Automate | Snap-ins | DevRev" }, { - "id": "ART-2575_KNOWLEDGE_NODE-27", - "text": "initiate the process. Notifications about successful imports and any errors will appear in the form of toasts at the bottom left.\\n\\nCSV file requirements\\n---------------------\\n\\n### Mandatory fields\\n\\nTo ensure a successful import, certain fields are required.\\n\\n**Accounts**:\\n\\n* display\\\\_name\\n* external\\\\_refs (a unique identifier for the account, such as the company\\'s website domain.)\\n\\n**Contacts:**\\n\\n* display\\\\_name\\n* external\\\\_ref (a unique identifier for the contact, such as", - "title": "Account and contact import | Computer for Growth Teams | DevRev" + "id": "ART-12395_KNOWLEDGE_NODE-27", + "text": "update**: Link multiple accounts using /slack\\\\_broadcaster\\\\_upload external or /slack\\\\_broadcaster\\\\_upload internal and upload a CSV with account display names and Slack channel IDs.\\n* **Internal release notes**: Share internal updates by uploading a CSV with channel names and IDs using /slack\\\\_broadcaster\\\\_upload internal.\\n* **Configuration management**: Only authorized users in specific groups can post to Slack channels.\\n\\nSlash Commands\\n--------------\\n\\nThe Slack Broadcaster", + "title": "Slack Broadcaster | Automate | Snap-ins | DevRev" }, { - "id": "ART-2575_KNOWLEDGE_NODE-32", - "text": "required headers | Include headers for the required fields in the CSV. |\\n\\n[PreviousContacts](/docs/product/customers)[NextGrow snap-ins](/docs/product/snapins-grow)\\n\\n#### On this page\\n\\n* [Import data](#import-data)\\n* [CSV file requirements](#csv-file-requirements)\\n* [Mandatory fields](#mandatory-fields)\\n* [Array fields](#array-fields)\\n* [Tags](#tags)\\n* [Owner fields](#owner-fields)\\n* [Limitations](#limitations)\\n* [Troubleshooting](#troubleshooting)\\n\\n[Enterprise grade security to", + "id": "ART-2575_KNOWLEDGE_NODE-26", + "text": "the sample CSV.\\n\\n ![]()\\n\\n Columns with headers that do not conform to the predefined schema will not be imported.\\n4. In the dialog box, upload the populated CSV file.\\n5. (Optional) Configure import settings.\\n\\n * **Add tags to identify new imports**: Attach any existing tags to new imports for easy identification post-import.\\n * **Update existing accounts**: Select to update existing accounts by appending new values, rather than creating new objects.\\n6. Click **Import** to", "title": "Account and contact import | Computer for Growth Teams | DevRev" }, { - "id": "ART-2575_KNOWLEDGE_NODE-31", - "text": "Pre-create the tag in the app before importing. |\\n| Account with external reference \\'non-existing-account\\' not found | Ensure the parent account exists in the app before importing. |\\n| Mandatory field \\'external\\\\_refs\\' is empty | Fill all mandatory fields in the CSV. |\\n| Found non utf-8 character | Export the CSV with UTF-8 encoding. |\\n| Input CSV has no rows | Ensure the CSV contains data rows. |\\n| No user found with email | Ensure the email is correct and not a name. |\\n| Missing", - "title": "Account and contact import | Computer for Growth Teams | DevRev" + "id": "ART-8442_KNOWLEDGE_NODE-8", + "text": "import](/docs/product/account-contact-import)\\n * [Grow snap-ins](/docs/product/snapins-grow)\\n\\n * [Snap-ins](/docs/snapins)\\n\\n * [Automate](/docs/automate)\\n\\n * [Account deduplication](/docs/automations/account-deduplication)\\n * [Airtable](/docs/automations/airtable)\\n * [Auto-link DevRev GitHub accounts](/docs/automations/auto-link-github-devrev)\\n * [Automatic customer reply](/docs/automations/auto-reply)\\n * [Auto parts to", + "title": "January 2025 | Changelog | DevRev" }, { - "id": "ART-2575_KNOWLEDGE_NODE-11", - "text": "uploader](/docs/automations/csv-work-item-uploader)\\n - [CSV comments uploader](/docs/automations/csv-comments-uploader)\\n - [CSV commands uploader](/docs/automations/csv-commands-uploader)\\n - [Descope identity validation](/docs/automations/descope-identity-validation)\\n - [Effort logger](/docs/automations/effort-logger)\\n - [HTTP archive file upload & sanitization](/docs/automations/har-sanitization)\\n - [Link preview](/docs/automations/link-preview)\\n - [Org tags", - "title": "Account and contact import | Computer for Growth Teams | DevRev" + "id": "ART-13083_KNOWLEDGE_NODE-8", + "text": "import](/docs/product/account-contact-import)\\n * [Grow snap-ins](/docs/product/snapins-grow)\\n\\n * [Snap-ins](/docs/snapins)\\n\\n * [Automate](/docs/automate)\\n\\n * [Account deduplication](/docs/automations/account-deduplication)\\n * [Airtable](/docs/automations/airtable)\\n * [Auto-link DevRev GitHub accounts](/docs/automations/auto-link-github-devrev)\\n * [Automatic customer reply](/docs/automations/auto-reply)\\n * [Auto parts to", + "title": "| Automate | Snap-ins | DevRev" + }, + { + "id": "ART-2666_KNOWLEDGE_NODE-8", + "text": "import](/docs/product/account-contact-import)\\n * [Grow snap-ins](/docs/product/snapins-grow)\\n\\n * [Snap-ins](/docs/snapins)\\n\\n * [Automate](/docs/automate)\\n\\n * [Account deduplication](/docs/automations/account-deduplication)\\n * [Airtable](/docs/automations/airtable)\\n * [Auto-link DevRev GitHub accounts](/docs/automations/auto-link-github-devrev)\\n * [Automatic customer reply](/docs/automations/auto-reply)\\n * [Auto parts to", + "title": "October 5: Left navigation | Changelog | DevRev" }, { - "id": "ART-2575_KNOWLEDGE_NODE-29", - "text": "Tags\\n\\nEnsure all tags listed in the CSV file already exist within the application. Tags are not created automatically during the import process to prevent errors and maintain control. For example, if your CSV contains a tag in the tags.name column such as Q3FY25\\\\_CSS\\\\_Forum\\\\_Bay\\\\_Area, ensure to create the tag in the system first.\\n\\n### Owner fields\\n\\nFor accounts, owner information must be provided in email format. Avoid using names or display names.\\n\\nLimitations\\n-----------\\n\\nThe", + "id": "ART-2575_KNOWLEDGE_NODE-28", + "text": "a database identifier or an email address.)\\n* account\\\\_external\\\\_reference (the external reference of the contact\\'s parent account)\\n\\n### Array fields\\n\\nFor fields that accept multiple values, such as **owners** and **industry**, values should be separated by commas (,). For example, Agriculture and Forestry should be written as Agriculture,Forestry.\\n\\n![]()\\n\\nIf a value contains a comma, enclose it in backticks. For example, enter \"Rail, Bus & Taxi\" as `Rail, Bus & Taxi`.\\n\\n###", "title": "Account and contact import | Computer for Growth Teams | DevRev" }, { - "id": "ART-2575_KNOWLEDGE_NODE-24", - "text": "[Product demos](/docs/DevRevU/demos)\\n\\nOn this page\\n\\n* [Import data](#import-data)\\n* [CSV file requirements](#csv-file-requirements)\\n* [Mandatory fields](#mandatory-fields)\\n* [Array fields](#array-fields)\\n* [Tags](#tags)\\n* [Owner fields](#owner-fields)\\n* [Limitations](#limitations)\\n* [Troubleshooting](#troubleshooting)\\n\\n1. [Documentation](/docs)\\n3. [Computer for Growth Teams](/docs/product/grow)\\n[Account and contact import](/docs/product/account-contact-import)\\n\\nAccount and", + "id": "ART-2575_KNOWLEDGE_NODE-31", + "text": "Pre-create the tag in the app before importing. |\\n| Account with external reference \\'non-existing-account\\' not found | Ensure the parent account exists in the app before importing. |\\n| Mandatory field \\'external\\\\_refs\\' is empty | Fill all mandatory fields in the CSV. |\\n| Found non utf-8 character | Export the CSV with UTF-8 encoding. |\\n| Input CSV has no rows | Ensure the CSV contains data rows. |\\n| No user found with email | Ensure the email is correct and not a name. |\\n| Missing", "title": "Account and contact import | Computer for Growth Teams | DevRev" } ] @@ -5044,54 +5044,54 @@ "query": "how to build an agent", "retrievals": [ { - "id": "ART-15618_KNOWLEDGE_NODE-9", - "text": "reduced barriers to entry\\n\\nAgentExchange Marketplace : Largest marketplace of ready-made agents, actions, and topics for faster deployment\\n\\nEnterprise Security : Field-based data masking, RBAC, Einstein Trust Layer battle-tested at Fortune 100 scale\\n\\nMultilingual Support : Supports AI prompts and agent behavior across 25+ languages natively\\n\\nNative Integrations : Extensive integration ecosystem due to market dominance and longevity\\n\\nAdvanced Tooling : Deep debugging tools, bulk", - "title": "SF Agentforce - Competitive - for the PLuG on website" + "id": "ART-4167_KNOWLEDGE_NODE-3", + "text": "agents summarize critical context and escalate to the right person.\\n\\n![]()\\n\\nSet up is simple. Maintenance is simpler.\\n\\nSet up Computer in minutes and build agents using plain English. No PhD in AI required.\\n\\n### A few lines of code\\n\\nA few lines of code\\n\\nGet Computer's CX agent running with just a few lines of code and automatically track real performance metrics to measure progress against your goals.\\n\\n![]()\\n\\n### Built-in integrations\\n\\n### Agent", + "title": "Computer for Your Customers: AI Self-Service Support | DevRev" + }, + { + "id": "ART-15799_KNOWLEDGE_NODE-3", + "text": "agents summarize critical context and escalate to the right person.\\n\\n![]()\\n\\nSet up is simple. Maintenance is simpler.\\n\\nSet up Computer in minutes and build agents using plain English. No PhD in AI required.\\n\\n### A few lines of code\\n\\nA few lines of code\\n\\nGet Computer's CX agent running with just a few lines of code and automatically track real performance metrics to measure progress against your goals.\\n\\n![]()\\n\\n### Built-in integrations\\n\\n### Agent", + "title": "Computer for Your Customers: AI Self-Service Support | DevRev" }, { "id": "ART-13178_KNOWLEDGE_NODE-69", - "text": "data.\\n\\n * Define your agent\\xe2\\x80\\x99s specific goal and purpose.\\n * Write clear instructions for its operation.\\n * Connect your business knowledge and existing workflows.\\n\\nEvery team gains powerful capabilities without technical skills. It\\xe2\\x80\\x99s like having expert analysts and operators working 24/7.\\n\\nNeed to route customer requests? Create sales materials? Recommend support actions? All possible without writing a single line of code, including the generation of original", + "text": "data.\\n\\n * Define your agent\\xe2\\x80\\x99s specific goal and purpose.\\n * Write clear instructions for its operation.\\n * Connect your business knowledge and existing workflows.\\n\\nEvery team gains powerful capabilities without technical skills. It\\xe2\\x80\\x99s like having expert analysts and operators working 24/7.\\n\\nNeed to route customer requests? Create sales materials? Recommend support actions? All possible without writing a single line of code, including the generation of original", "title": "Understanding Agentic AI: Capabilities and Implications for the Future" }, { - "id": "ART-15618_KNOWLEDGE_NODE-15", - "text": "behavior\\n\\nDevRev : AI-native architecture offering outcome-driven workflows and intuitive, conversational agents User Experience\\n\\nAgentforce : Multiple tabs, nested screens, fragmented multi-stage agent creation process\\n\\nDevRev : Consolidated actions, modern agent-first UX, single cohesive screen for agent building Learning Capabilities\\n\\nAgentforce : Manual improvements, no learning from real usage or customer interactions\\n\\nDevRev : Auto-learning by identifying knowledge gaps", - "title": "SF Agentforce - Competitive - for the PLuG on website" + "id": "ART-3880_KNOWLEDGE_NODE-5", + "text": "Agent (formerly PLuG) setup remarkably simple:\\n\\nThe initial setup was very straightforward. It didn't take long to get it running in my local development environment, and I didn't even need to reach out for support - that was great.\\n\\n![]()\\n\\nBrian MullinSr. Software Engineer, Orum\\n\\nThe process began with adding the script tag and initializing the SDK on the frontend, followed by obtaining an access token via the backend. This smooth onboarding experience enabled Brian to focus on", + "title": "How Orum built a collaborative, AI-ready support engine" }, { - "id": "ART-13178_KNOWLEDGE_NODE-19", - "text": "interact with the agentic AI system using natural language. Unlike traditional systems requiring precise commands, you communicate conversationally. The autonomous agents interpret your intent and may ask clarifying questions.\\n 2. **Agent system plans, allocates, and executes work:** The system transforms your request into [structured workflows](/blog/native-workflow-engine), dividing it into tasks and subtasks. A managing component assigns these to specialized subagents.\\n 3. **Agent system", - "title": "Understanding Agentic AI: Capabilities and Implications for the Future" + "id": "ART-4206_KNOWLEDGE_NODE-4", + "text": "create a webhook to receive agent execution events:\\n\\nBashJavaScript\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl --location \\'https://api.devrev.ai/internal/webhooks.create\\' \\\\ |\\n| > | --header \\'Content-Type: application/json\\' \\\\ |\\n| > | --header \\'Authorization: Bearer \\' \\\\ |\\n| > | --data \\'{ |\\n| > | \"url\": \"https://your-application.com/webhook-endpoint\", |\\n| > | \"event_types\": [\"ai_agent_response\"], |\\n| > | \"headers\": [ |\\n| > | { |\\n| > | \"name\": \"x-api-key\", |\\n| >", + "title": "Agents async API | DevRev | Docs" }, { - "id": "ART-15618_KNOWLEDGE_NODE-10", - "text": "testing via CSV uploads, auto-generation of test cases\\n\\nOutbound Capabilities : Supports automated outreach campaigns and lead nurturing sequences\\n\\nRich UI Elements : Agents can display buttons, forms, and visuals across different platforms\\n\\nMuleSoft Integration : Can turn existing APIs into agent actions using plain language Agentforce Weaknesses\\n\\nForced Migration : With Live Agent being deprecated, customers are pushed toward Agentforce with a \"take it or leave it\"", - "title": "SF Agentforce - Competitive - for the PLuG on website" + "id": "ART-12585_KNOWLEDGE_NODE-7", + "text": "prompts, logic, and agent configurations for accuracy, reliability, and scalability.\\n* **Own Requirements**: Partner with customers to deeply understand their needs and translate them into technical agent specifications.\\n* **Prototype & Iterate**: Lead live demos, build rapid proof-of-concepts, and refine solutions through customer feedback.\\n* **Lead Execution**: Define project plans, align internal teams, and ensure timely delivery of deployments.\\n* **Advise Customers**: Act as a trusted", + "title": "DevRev Careers | Forward Deployed Engineer" }, { - "id": "ART-13178_KNOWLEDGE_NODE-39", - "text": "agents incorporate medical knowledge and compliance requirements, while financial agents understand regulatory frameworks and transaction patterns.\\n\\n### 3\\\\. Orchestration frameworks\\n\\nOrchestration components coordinate multiple AI agents working together. They manage workflows, handle exceptions, and maintain performance standards. This capability is crucial when deploying complex multi-agent systems across departments.\\n\\n### 4\\\\. Integration capabilities\\n\\nYour platform must connect", + "id": "ART-13178_KNOWLEDGE_NODE-71", + "text": "real-world setting**\\n * **Train your own AI Agent using DevRev**\\n * **Connect the tools you already use**\\n * **Go from demo to deployment in days**\\n\\n _Just reach out. Let\\xe2\\x80\\x99s make Agentic AI work for you._ [**Book a demo.**](/request-a-demo)\\n\\n### Frequently Asked Questions\\n\\n###\\n\\nWhat are the main components of Agentic AI systems?\\n\\n__\\n\\n###\\n\\nCan small businesses benefit from Agentic AI platforms?\\n\\n__\\n\\n###\\n\\nWhat makes Agentic AI different from chatbots and", "title": "Understanding Agentic AI: Capabilities and Implications for the Future" }, { - "id": "ART-15618_KNOWLEDGE_NODE-8", - "text": "doesn\\'t inherit legacy tech debt.\\n\\nShield 2: AgentExchange Offers the Largest Marketplace\\n\\nSalesforce buyers can customize and use prebuilt agents across industries, making it easy to go live quickly. DevRev offers a growing set of templates, but the depth and breadth of AgentExchange are currently unmatched. Detailed Strengths and Weaknesses Analysis Agentforce Strengths\\n\\nMarket Position : Service Cloud is one of the most common systems of record, making Agentforce an easy upsell with", - "title": "SF Agentforce - Competitive - for the PLuG on website" + "id": "ART-4206_KNOWLEDGE_NODE-0", + "text": "b'Agents async API | DevRev | Docs\\n\\n[![]()![]()](https://developer.devrev.ai/)\\n\\nBeta\\n\\nBeta\\n\\nBeta\\n\\nSearch\\n\\n`/`\\n\\nOn this page\\n\\n* [Set up webhook](/beta/guides/agents-async-api#set-up-webhook)\\n* [Make async API calls](/beta/guides/agents-async-api#make-async-api-calls)\\n* [Handle webhook events](/beta/guides/agents-async-api#handle-webhook-events)\\n* [Progress messages](/beta/guides/agents-async-api#progress-messages)\\n* [Final", + "title": "Agents async API | DevRev | Docs" }, { - "id": "ART-15618_KNOWLEDGE_NODE-11", - "text": "approach\\n\\nPlatform Dependency : Cannot run without Salesforce as system of record, incompatible with modern tools like Zendesk and Intercom\\n\\nComplex Setup : Overwhelms users with dozens of setup steps and dependencies, steep learning curve even for skilled users\\n\\nLegacy Architecture : Built on traditional CRM architecture with rigid underlying schema resulting in slower, more brittle agents\\n\\nPartner Dependency : 70% of implementations require partners, demanding heavy admin", - "title": "SF Agentforce - Competitive - for the PLuG on website" + "id": "ART-15621_KNOWLEDGE_NODE-9", + "text": "engineering)\\n\\nEach agent requiring individual configuration\\n\\nOperational complexity through multiple specialized systems\\n\\nSeparate prompt library and agent library adding user complexity\\n\\nDevRev Approach : Unified agent architecture\\n\\nSingle interface with dynamic skill loading per user requests\\n\\nEliminates operational overhead through centralized management\\n\\nPredictable performance model with coupled AI agent-LLM architecture\\n\\nConsistent reasoning patterns ensuring reliable", + "title": "Glean - Competitive - for the PLuG on website" }, { - "id": "ART-13178_KNOWLEDGE_NODE-41", - "text": "reasons.\\n\\n### 6\\\\. Development tools\\n\\nThe platform\\xe2\\x80\\x99s development environment significantly impacts customization capabilities. Low-code interfaces enable business users to modify agent behavior without technical expertise. Developer-focused systems offer greater flexibility but require coding skills. DevRev provides both options, supporting different organizational capabilities.\\n\\n### 7\\\\. Pricing structures\\n\\nPricing models vary significantly between vendors.", + "id": "ART-13178_KNOWLEDGE_NODE-19", + "text": "interact with the agentic AI system using natural language. Unlike traditional systems requiring precise commands, you communicate conversationally. The autonomous agents interpret your intent and may ask clarifying questions.\\n 2. **Agent system plans, allocates, and executes work:** The system transforms your request into [structured workflows](/blog/native-workflow-engine), dividing it into tasks and subtasks. A managing component assigns these to specialized subagents.\\n 3. **Agent system", "title": "Understanding Agentic AI: Capabilities and Implications for the Future" - }, - { - "id": "ART-4206_KNOWLEDGE_NODE-4", - "text": "create a webhook to receive agent execution events:\\n\\nBashJavaScript\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl --location \\'https://api.devrev.ai/internal/webhooks.create\\' \\\\ |\\n| > | --header \\'Content-Type: application/json\\' \\\\ |\\n| > | --header \\'Authorization: Bearer \\' \\\\ |\\n| > | --data \\'{ |\\n| > | \"url\": \"https://your-application.com/webhook-endpoint\", |\\n| > | \"event_types\": [\"ai_agent_response\"], |\\n| > | \"headers\": [ |\\n| > | { |\\n| > | \"name\": \"x-api-key\", |\\n| >", - "title": "Agents async API | DevRev | Docs" } ] }, @@ -5100,55 +5100,55 @@ "query": "multiple messages sent quickly AI interpretation delay", "retrievals": [ { - "id": "ART-990_KNOWLEDGE_NODE-1", - "text": "and is a good thing; it alerts us that a fundamental shift is happening, just like the internet had done previously. And, no, this isn\\xe2\\x80\\x99t the beginning of SkyNet.\\n\\n\\n\\nLet\\xe2\\x80\\x99s face it; support is moving to a more asynchronous communication model (a-la chat). With the ability for ChatGPT to \\xe2\\x80\\x9cstream\\xe2\\x80\\x9d messages similar to how a user would, backed by the knowledge of the internet, the result can be a very powerful one-two punch. Plus, it can eliminate a lot", - "title": "To AI, or Not to AI for Support, It's Not a Question" + "id": "ART-1640_KNOWLEDGE_NODE-20", + "text": "260| \"namespace\": \"ai_assistant_message\", \\n 261| \"raw_email_artifact\": { \\n 262| \"id\": \"id\", \\n 263| \"display_id\": \"display_id\", \\n 264| \"file\": { \\n 265| \"type\": \"type\", \\n 266| \"name\": \"name\", \\n 267| \"size\": 1 \\n 268| } \\n 269| }, \\n 270| \"sent_timestamp\": \"sent_timestamp\", \\n 271| \"subject\": \"subject\", \\n 272| \"text_body\": \"text_body\" \\n 273| } \\n 274|", + "title": "Create Snap Widget (Beta) \u2014 DevRev | Docs" }, { - "id": "ART-990_KNOWLEDGE_NODE-5", - "text": "assistance whenever they need it, irrespective of geographical and time zone differences.\\n For a follow-the-sun model this may be less important, however, if you don\\xe2\\x80\\x99t have this coverage in place, an AI-assist can be extremely valuable to provide coverage between gaps\\n\\n\\nPersonalization\\n\\n\\n By leveraging natural language processing and machine learning, ChatGPT and similar tools can understand customers\\xe2\\x80\\x99 needs and preferences, providing personalized and contextually", - "title": "To AI, or Not to AI for Support, It's Not a Question" + "id": "ART-4206_KNOWLEDGE_NODE-13", + "text": "2 | \"payload\": { |\\n| 3 | \"ai_agent_response\": { |\\n| 4 | \"agent\": \"don:core:dvrv-us-1:devo/xyz:ai_agent/123\", |\\n| 5 | \"agent_response\": \"message\", |\\n| 6 | \"client_metadata\": { |\\n| 7 | /* your original metadata */ |\\n| 8 | }, |\\n| 9 | \"message\": \"The agent\\'s final response message\", |\\n| 10 | \"session\": \"don:core:dvrv-us-1:devo/xyz:ai_agent_session/3810\", |\\n| 11 | \"session_object\": \"unique_conversation_identifier\" |\\n| 12 | }, |\\n| 13 | \"type\": \"ai_agent_response\" |\\n| 14 | } |\\n| 15 | }", + "title": "Agents async API | DevRev | Docs" }, { - "id": "ART-990_KNOWLEDGE_NODE-3", - "text": "multiple customer queries simultaneously, significantly reducing response times and providing instant support, resulting in higher customer satisfaction levels.\\n By offloading the initial responses to an intelligent system, you can buffer the amount of time a traditional agent has to respond\\n This may also help ensure you meet you SLA requirements\\n\\n\\nCost-Effectiveness\\n\\n\\n AI-driven customer support tools can minimize the need for large customer service teams, reducing operational", - "title": "To AI, or Not to AI for Support, It's Not a Question" + "id": "ART-4109_KNOWLEDGE_NODE-1", + "text": "-X POST https://api.devrev.ai/ai-agents.events.execute-async \\\\ |\\n| > | -H \"Authorization: Bearer \" \\\\ |\\n| > | -H \"Content-Type: application/json\" \\\\ |\\n| > | -d \\'{ |\\n| > | \"agent\": \"string\", |\\n| > | \"event\": { |\\n| > | \"input_message\": { |\\n| > | \"message\": \"string\" |\\n| > | } |\\n| > | }, |\\n| > | \"session_object\": \"string\" |\\n| > | }\\' |\\n```\\n\\n[Try it](/beta/api-reference/ai-agents/ai-agent-events-execute-async?explorer=true)\\n\\n200Successful\\n\\n```\\n| | |\\n| --- | --- |\\n| 1", + "title": "Execute-Async Ai Agents Events | DevRev | Docs" }, { - "id": "ART-990_KNOWLEDGE_NODE-9", - "text": "While this is likely a edge case, you can easily account for this with logic in the system than can allow the user or system to automatically switch the interaction to a support engineer.\\n\\n\\nLack of empathy\\n\\n\\n Chatbots may struggle to replicate the empathy and human touch that customer service representatives provide. In sensitive or emotionally charged situations, an AI-driven response may appear impersonal or unsympathetic, negatively impacting customer relations.\\n This is both a good", - "title": "To AI, or Not to AI for Support, It's Not a Question" + "id": "ART-2027_KNOWLEDGE_NODE-41", + "text": "AI to improve tone, grammar, or length of your message. |\\n| Preview & Expand View | Expand icon (top-right of editor) | Open full-screen view to preview and edit the outgoing message as it would appear to the customer. |\\n| Include Conversation History | Three-dot menu (bottom-right) | Shows previous non-editable email exchanges. Default inclusion can be set in snap-in settings. |\\n| Use Slash Commands | Lightning icon (bottom-left) | Insert templated responses or quick actions using slash", + "title": "Email | Integrate | Snap-ins | DevRev" }, { - "id": "ART-4206_KNOWLEDGE_NODE-19", - "text": "const conversationId = |\\n| 38 | event.payload.ai_agent_response.client_metadata.conversation_id; |\\n| 39 | |\\n| 40 | if (event.payload.ai_agent_response.agent_response === \"message\") { |\\n| 41 | // Final message |\\n| 42 | const message = event.payload.ai_agent_response.message; |\\n| 43 | sendToClient(conversationId, { |\\n| 44 | type: \"agent_response\", |\\n| 45 | message: message, |\\n| 46 | }); |\\n| 47 | } else if (event.payload.ai_agent_response.agent_response === \"error\") { |\\n| 48 | // Error", - "title": "Agents async API | DevRev | Docs" + "id": "ART-4271_KNOWLEDGE_NODE-31", + "text": "AI-handled conversation reaches its capability limits and needs human expertise.\\n * **Extended troubleshooting** : Issues requiring multiple steps or follow-ups over time.\\n\\n## Key information\\n\\n * **Channel support** : Currently, the conversion feature is only available for PLuG and Slack conversations. Other channels still use the traditional **Link Ticket** functionality.\\n\\n * **CSAT surveys** : CSAT surveys are not sent when a conversation is converted to a ticket. Surveys are only", + "title": "Convert Conversations to Tickets | Conversations | Support | DevRev" }, { - "id": "ART-4109_KNOWLEDGE_NODE-5", - "text": "Error\\n\\n429\\n\\nToo Many Requests Error\\n\\n500\\n\\nInternal Server Error\\n\\n503\\n\\nService Unavailable Error\\n\\nWas this page helpful?\\n\\nYesNo\\n\\n[Previous](/beta/api-reference/accounts/update)[#### Get Airdrop Sync Unit\\n\\nNext](/beta/api-reference/airdrop/sync-units-get)[Built with](https://buildwithfern.com/?utm_campaign=buildWith&utm_medium=docs&utm_source=developer.devrev.ai)'", - "title": "Execute-Async Ai Agents Events | DevRev | Docs" + "id": "ART-15509_KNOWLEDGE_NODE-13", + "text": "unread messages and display them to the user.\\n* `ON_CONVERSATION_START`: Indicates that the user has started a new conversation.\\n* `ON_SEARCH_AGENT_QUERY`: Indicates that a new search query has been made in the Plug search agent.\\n* `ON_OBSERVABILITY_READY`: Triggered when the session analytics capabilities of Plug are initialized.\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | useEffect(() => { |\\n| 2 | window.plugSDK.onEvent((payload) => { |\\n| 3 | if (payload.type === PAYLOAD_TYPE) { |\\n| 4 |", + "title": "Methods | DevRev | Docs" }, { - "id": "ART-990_KNOWLEDGE_NODE-0", - "text": "b'\\n\\n\\n \\xe2\\x80\\x9cThe greatest danger in times of turbulence is not the turbulence; it is to act with yesterday\\xe2\\x80\\x99s logic.\\xe2\\x80\\x9d - Peter Drucker\\n\\n\\n\\n\\n\\xe2\\x80\\xa6\\n\\nAt this point, you\\xe2\\x80\\x99ve likely been inundated with with the news of AI, LLM, GPT, or ChatGPT. Hint: GPT stands for \"Generative Pre-trained Transformer\". And it likely begs a few questions\\xe2\\x80\\xa6 Is this the start of SkyNet? Will I become irrelevant? And a multitude of others. This anxiety is OK", - "title": "To AI, or Not to AI for Support, It's Not a Question" + "id": "ART-1301_KNOWLEDGE_NODE-88", + "text": "Required\\nThe list of notifications to send.\\nShow variant\\nResponse.\\n\\nThis endpoint returns a map from strings to any.\\nAPI Reference conversations Create.\\n\\nPOST https:// api.devrev.ai / conversations.create\\nCreates a conversation.\\nRequest.\\n\\nThis endpoint expects an object.\\ntype \"support\" Required\\ndescription string Optional\\nDescription for the conversation.\\ngroup string Optional\\nThe group that the conversation is associated with.\\nis_spam boolean Optional\\nWhether the", + "title": "Delete \u2014 DevRev | Docs" }, { - "id": "ART-4206_KNOWLEDGE_NODE-20", - "text": "occurred |\\n| 49 | sendToClient(conversationId, { |\\n| 50 | type: \"agent_error\", |\\n| 51 | error: event.payload.ai_agent_response.error.error, |\\n| 52 | }); |\\n| 53 | } |\\n| 54 | |\\n| 55 | res.status(200).send(\"OK\"); |\\n| 56 | }); |\\n```\\n\\n##### \\n\\nUsing WebSockets or Server-Sent Events can provide real-time updates to your\\nUI as events are received.\\n\\n### Talk to agent node in workflows\\n\\n##### \\n\\nThis is in early access, please contact support to have it enabled for you.\\n\\nIf", - "title": "Agents async API | DevRev | Docs" + "id": "ART-1780_KNOWLEDGE_NODE-83", + "text": "Required\\nThe list of notifications to send.\\nShow variant\\nResponse.\\n\\nThis endpoint returns a map from strings to any.\\nAPI Reference conversations Create.\\n\\nPOST https:// api.devrev.ai / conversations.create\\nCreates a conversation.\\nRequest.\\n\\nThis endpoint expects an object.\\ntype \"support\" Required\\ndescription string Optional\\nDescription for the conversation.\\ngroup string Optional\\nThe group that the conversation is associated with.\\nis_spam boolean Optional\\nWhether the", + "title": "Get Post \u2014 DevRev | Docs" }, { - "id": "ART-990_KNOWLEDGE_NODE-2", - "text": "of the \\xe2\\x80\\x9cgrunt work\\xe2\\x80\\x9d (aka work \\xe2\\x80\\x9csuck\\xe2\\x80\\x9d) that support engineers commonly deal with, allowing them to focus on the real problems at hand.\\n\\nAlso, with this evolution to a semi-sentient system, the experience for end-users is far superior, sometimes to the point where you may not even know you\\xe2\\x80\\x99re conversing with a computer.\\n\\nBenefits\\n\\nHere are some of the potential benefits:\\n\\nEfficient Response Times\\n\\n\\n AI-powered chatbots can handle", - "title": "To AI, or Not to AI for Support, It's Not a Question" + "id": "ART-1302_KNOWLEDGE_NODE-88", + "text": "Required\\nThe list of notifications to send.\\nShow variant\\nResponse.\\n\\nThis endpoint returns a map from strings to any.\\nAPI Reference conversations Create.\\n\\nPOST https:// api.devrev.ai / conversations.create\\nCreates a conversation.\\nRequest.\\n\\nThis endpoint expects an object.\\ntype \"support\" Required\\ndescription string Optional\\nDescription for the conversation.\\ngroup string Optional\\nThe group that the conversation is associated with.\\nis_spam boolean Optional\\nWhether the", + "title": "Export \u2014 DevRev | Docs" }, { - "id": "ART-990_KNOWLEDGE_NODE-8", - "text": "natively\\n\\n\\n\\n\\nPotential Risks\\n\\n\\n\\nWhile the use of artificial intelligence and tools like ChatGPT offers numerous benefits in the realm of customer support, it is crucial to consider potential risks that may arise.\\n\\nSome of these risks include:\\n\\nMisunderstandings\\n\\n\\n AI-driven chatbots might misunderstand complex customer queries or interpret context inaccurately, leading to incorrect or irrelevant responses. This can result in customer frustration and diminished satisfaction.\\n", - "title": "To AI, or Not to AI for Support, It's Not a Question" + "id": "ART-15618_KNOWLEDGE_NODE-23", + "text": "better customer outcomes Key Messaging Frameworks\\n\\n\"AI-Native vs CRM-Constrained\" : Position DevRev as purpose-built for AI while Agentforce is constrained by legacy architecture\\n\\n\"Predictable vs Unpredictable\" : Emphasize transparent pricing against Salesforce\\'s complex cost structure\\n\\n\"Modern vs Legacy\" : Contrast clean, fast user experience with Salesforce\\'s acknowledged UI problems\\n\\n\"Simple vs Complex\" : Highlight streamlined implementation against partner-dependent", + "title": "SF Agentforce - Competitive - for the PLuG on website" } ] } -] \ No newline at end of file +]