Skip to main content

Understand & Plan

These are the read-only ways to use the Copilot. Nothing here changes your configuration, so it's the safest place to start — especially on an account you didn't build yourself. Ask how something works, get a second opinion on a flow, or think through an approach before you commit to it.

Because the Copilot reads your live configuration, its answers describe your actual flows, data points, and APIs — not a generic example. That makes it the fastest way to learn an unfamiliar setup.

Explain existing configuration​

Ask how a journey is handled, what a specific flow, data point, or API does, or where something is used. The Copilot traces the real wiring — which flow triggers, which objectives it collects, which data points feed it, and which custom API sits underneath.

"How is 'where is my order' handled for this customer?" "What does the sku_id data point do, and which flows use it?" "How does freshdesk_create_ticket work — what does it send and what does it return?" "Which flows would trigger if a customer says they want to cancel?" "What data points depend on a selected order?"

Good for: onboarding to a new account, confirming your mental model before a change, or finding the source of a value the customer is seeing.

Review or audit a flow​

Ask for a quality review with concrete improvement suggestions. The Copilot points out gaps, fragile conditions, unreachable steps, or missing handoffs — but does not apply anything. You decide what to act on.

"Review the warranty flow and suggest improvements." "Audit this flow for anything that could be cleaner or could break." "Are there any dead ends in the refund flow where the customer gets stuck?" "Does the cancellation flow handle the case where the order already shipped?"

After you save or apply a change, an Ask Copilot to review button appears under that reply. Clicking it sends a review request for the changed flow and the flows connected to it; your message shows as a short Review requested note (open Show full prompt to read the instructions sent). The review only suggests fixes and changes nothing.

When you're ready to act on the feedback, hand the specific change to Build & change flows.

Flow reviews check recent conversations​

When an account admin asks the Copilot to review a flow, it also checks how that flow behaved in real conversations over the last 30 days. It reads Conversation Audit findings on tickets that went through the flow, and Automation Gaps where the AI couldn't handle a customer's message while in it. It also reads gaps whose analysis lists the flow among the closest flows for a request it couldn't handle, including requests no flow covers yet, so the review can say what the flow could take on. These gaps still match after the flow is renamed. The review then adds an Evidence from Real Conversations section that groups the problems into themes, ties each to the part of the flow most likely behind it, and cites the tickets.

  • Since the last change. The check focuses on conversations after the flow was last saved. When only a few have arrived since then, older ones are included and labeled, and the review says how many of them the saved flow already handles. That makes a review right after a change a quick way to see whether it helped.
  • Only what this flow can fix. Findings about other flows or routing, problems that aren't actionable, gaps already dismissed or resolved on the Automation Gaps page, and findings a reviewer marked as wrong are left out. The review says how many items it checked and how many it left out.
  • Other flows. When a left-out problem belongs to another flow, such as a flow this one hands off to or the flow the customer was in, the review names that flow so you can review it next. It doesn't change the reviewed flow for them.
  • Other owners. Problems for the agent team, FAQs and business information, business operations, or a possible product defect are summarized in one line each instead of becoming flow changes.

The check runs for up to two flows per review, for account admins only. Other reviews, and accounts with no audits or gaps, review the configuration alone; a review never claims more conversations than it checked.

Plan an approach​

Ask for design direction before building. This is where to bring a fuzzy goal and let the Copilot help you shape it — including whether something should even be a flow at all.

"I want to support warranty eligibility — how should I set it up?" "Should delayed delivery be an FAQ or a flow?" "What's the cleanest way to collect an image and verify it before escalating?" "I need to route damaged-item claims differently from wrong-item claims — how should I structure that?"

A planning answer typically covers what to collect, where data comes from, where the conversation should branch, and when to hand off to a human — so you can turn it into a build request with confidence.

Find out why customers are unhappy​

When Unhappy Customer Reasons is turned on for the account, account admins can ask the Copilot why customers are unhappy and what to change. It reads the reasons behind your unhappy tickets, the same ones shown under Why customers are unhappy in Conversation Audits → Unhappy customers. Unhappy tickets are those with a low rating, or where the customer was frustrated, aggressive, threatened to escalate or disputed an outcome. The Copilot looks at example tickets for the top reasons and answers per owner:

  • Support setup reasons become concrete change proposals for flows, FAQs, AI answers or settings, each citing the tickets it rests on. Hand the ones you want to Build & change flows.
  • Agent team reasons become coaching points.
  • Business operations reasons (delivery, product, policy) become a summary you can take to the team that owns them; the Copilot doesn't try to fix those in configuration.

"Why is our CSAT low this month?" "Why are customers getting angry on refund requests?" "Which flows have the most escalation threats, and what should we change?"

The Copilot says how many unhappy tickets had a reason. Tickets whose conversation was never audited have none yet.

Getting better answers​

  • Name the specifics. "the warranty flow" and "the order_status data point" get precise answers; "the thing that checks orders" makes the Copilot guess.
  • Give the customer's words. For "how is this handled" questions, paste roughly what the customer would say — that's what actually decides which flow triggers.
  • Ask why, not just what. "Why would this flow not trigger for a returning customer?" surfaces the reasoning you'll need before changing anything.