Use Avo in your workspace

Open Home in a team workspace to use the full Avo chat. In an enterprise workspace, open Avo to ask questions across the enterprise and its teams.

​

Understand Avo’s scope

In a team workspace, Avo answers from the current team and the page context supplied by the dashboard. Its available data can include call performance, bookings, unbooked reasons, booking windows, transfer settings, workflows, scheduler statistics, and call-level diagnostics. In an enterprise workspace, Avo uses enterprise rollups, comparisons, trends, and team-level drill-downs for that enterprise. Select the information icon in the header to review the active scope. Avo is scoped to the current Avoca workspace and is not a public-web search tool.

​

Start a chat

Enter a question in the composer and send it. Enter sends the message; use Shift+Enter for a new line. While Avo is responding, you can stop the response. After a response finishes, use Regenerate to ask Avo to produce the latest answer again. Ask a specific question and include the time range, record identifier, or business unit when it matters. For example, a call investigation is more reliable with the call ID, while a dispatch investigation may need a date and job number or appointment ID.

​

Use quick prompts

The team Home workspace currently offers these shortcuts:

• Triage dispatch complaint
• Explain assignment decision
• Check out my booking windows
• Update booking windows for weekdays
• Why are calls going unbooked?
• What time of day has the best booking rate?
• Build a workflow

Selecting a quick prompt sends its request immediately; it does not only fill the composer. The current Update booking windows for weekdays shortcut requests weekdays from 8:00 AM to 5:00 PM as regular-only availability. Use it only when that is the intended configuration, and verify the saved booking windows afterward. Enterprise Avo uses enterprise-specific prompts for summarizing performance, finding teams that need attention, comparing call trends, and deciding what to inspect next.

​

Review Avo action proposals

Avo can read and explain workspace data without changing it. When a supported request would write configuration, Avo presents an Approval required card instead of applying the change immediately. The card is the source of truth for the proposed action: review its team scope, target, and exact change details rather than relying only on the surrounding chat explanation. For teams with Fees access, supported proposals can include creating one fee, updating an existing fee amount or customer-facing description, replacing an enabled fee ruleset’s complete condition set, and changing supported promotion or holiday-fee links. These actions do not let Avo create or delete a fee ruleset or change its arrival-window assignments. Only the user who owns the proposal can approve or deny it. Approve runs the stored action once and immediately; it is not undone automatically. A high-impact action uses Review & approve and requires a second confirmation. Deny leaves the configuration unchanged. Proposals expire. They also verify the current saved value before execution, so an approval can fail safely when another person changed the same configuration after the card was prepared. In that case, ask Avo to read the latest state and prepare a new proposal. After any successful write, open the affected dashboard setting and verify the result before relying on it for live traffic.

​

Investigate booking rate from call analytics

When enabled, How can I improve my booking rate? appears beside Call Metrics on the Calls page and Call Analytics on the Responder Overview. Selecting it opens Avo, starts a new conversation, and immediately sends a request to sample recent bookable unbooked calls, group the underlying failure modes, recommend concrete fixes, and identify which fix to prioritize. This button sends the request; it does not only open a blank composer. Review the answer’s call sample, links, time range, and definitions before acting. Avo’s analysis does not change call classifications, booking windows, workflows, or other configuration by itself.

​

Start a new chat or reopen history

Avo saves completed conversations to the current team or enterprise workspace.

• Select New chat in the header to clear the current thread and start another. This does not delete the saved conversation.
• Select Conversation history to reopen a recent thread.
• History separates Your conversations from conversations Shared with you.
• You can permanently delete a conversation you own. Deleting it also makes its shared link stop working.

Deleting a saved conversation cannot be undone. Starting a new chat is the safer choice when you only want a clean composer.

​

Share a conversation

After a normal Avo or Analyst conversation is saved, its share control can offer Share and copy link. Only the conversation owner can start or stop sharing. An Analyst share link reopens the saved question in Analyst mode for an eligible team recipient. A share link is not public: the recipient must sign in and have access to the same team or enterprise. A shared conversation is read-only for the recipient. If the recipient replies, Avo starts a new private copy instead of changing the owner’s thread. Use Stop sharing when the link should no longer work. Review the entire thread before sharing because the recipient can see the saved conversation, including any customer or operational details included in it.

​

Use Analyst when available

Analyst is an optional, team-only mode. When full Analyst access is enabled, select Analyst or Try Analyst to switch from regular chat. Analyst offers preset analyses for:

• Canceled jobs and rebooking opportunities
• Marketing budget and lead-source performance
• Revenue lost to low-performing technicians or CSRs
• Seasonal service progress for members
• Dormant customers with aging equipment
• Recoverable revenue across open opportunities

Analyst currently depends on supported ServiceTitan data, an enabled CRM Integration, and analysis that has caught up to the current day. Follow the status shown in the workspace if the CRM is unsupported, disconnected, paused, or still being analyzed. Analyst keeps a separate Past questions history and uses New question instead of New chat. Saved Analyst questions use the same owner-controlled sharing rules described above. When enabled for the team, each Analyst question shows a Deep Analysis progress card. The card stays with that question and changes from working to finished as steps such as gathering context, checking business data, analyzing results, preparing a visual or export, and preparing the answer complete. A step can also show that it could not complete, and stopping a response marks unfinished progress as stopped. The progress card describes what Analyst attempted; it is not an additional result or proof that the final figures are correct. Review the answer, time range, source records, and any export before acting on it. Some teams see only an Analyst early-access preview. In that state, questions and presets are disabled and Get Access submits an interest request; it does not run an analysis.