Skip to main content
This page walks through what working with Ask Dimedove looks like day to day: how you ask a question, what you get back, and how proposed changes are reviewed and applied.

​
Starting a Conversation

Open Ask Dimedove from the home page prompt box or the button in the top navigation, then describe what you want in plain language. A few examples:
  • Search across all your conversations
  • Review how an agent is configured
  • Count conversations by channel
  • Rewrite an agent’s instructions
  • Surface insights collected about a contact
  • Adjust an agent’s tone or personality
  • Summarize what happened this week
You can mention a specific agent, channel, or label in your message to point the copilot at exactly what you mean. This is helpful when you have several agents or channels and want to be precise.
Save prompts you use often so you can reuse them later without retyping. Saved prompts are available from the composer while you chat.

​
Reading the Results

As Ask Dimedove works, it shows its progress in the conversation:
  • Thinking: A short, collapsible summary of the copilot’s reasoning as it works through your request
  • Activity: Labels for what it is doing, such as searching conversations or reading an agent’s configuration
  • Result cards: Rich, readable cards for the data it finds, including conversations, contacts, agents, and channels
Result cards are built for skimming, so you can see the important details at a glance and open the full record when you need more.

​
Reviewing and Approving Changes

Ask Dimedove can do more than answer questions. It can also propose changes to your agent and channel configurations. To keep you in control, those changes are never applied automatically. When the copilot proposes a change, you see a proposal card in the conversation:
  1. Review: The card shows exactly what would change. For instructions, you see a before and after comparison. For other settings, you see the current value next to the proposed value.
  2. Decide: Choose to approve or reject the proposal.
  3. Apply: If you approve, the change is saved. If you reject, nothing changes and you can refine your request.
Some changes, such as social channel comment instructions, save and go live as soon as you approve them. Agent configuration changes are saved as a draft first, so you can publish them to your live agent when you are ready. See Versions for how drafts and publishing work for agents.
This review step means you can ask the copilot to make sweeping edits with confidence: you always see the change and approve it before it affects a live agent or channel.

​
Disambiguation

If a request could apply to more than one agent, Ask Dimedove will ask you to choose which one before it continues. This prevents changes from landing on the wrong agent and keeps your intent clear.

​
Credits and Usage

Each turn in a conversation with Ask Dimedove consumes Work Credits based on the complexity of the request. Quick lookups use fewer credits than deep analysis or larger proposed changes. You can see your copilot usage for the current period, including how much of your team’s allowance has been used, directly in the product.
Work Credits are shared across the platform. For the full picture of how credits are allocated and tracked, see Credits.

​
Tips for Better Results

  • Be specific: Mention the agent, channel, or label you mean so the copilot targets the right record
  • Start broad, then narrow: Ask for a summary or a count first, then drill into the conversations that matter
  • Iterate on changes: If a proposed edit is not quite right, reject it and refine your request rather than approving and redoing it
  • Keep context in one chat: Follow-up questions in the same conversation build on what came before