AI drafts & intent
Assure Pro has four AI surfaces in Communications. Each does one thing well — and none of them sends anything without your approval.
| Surface | What it does | Where to find it |
|---|---|---|
| Intent badge | Tags incoming messages with a category | Header next to the client name, and on each incoming bubble |
| Suggested actions | One-click chips that draft an action or reply | Above the compose form |
| AI Draft | Drafts a reply from thread context | Compose form (the sparkle button) |
| Thread summary | A short recap of the whole thread | Card above the message stream |
Below — each one in detail.
How intent badges work
Every incoming message is tagged with an intent. The badge appears on:
- The client row in the inbox (latest incoming tag).
- The thread header (latest incoming tag).
- The message bubble itself (the message’s own tag — hover to expand).
The seven intents
| Intent | Meaning | Badge color |
|---|---|---|
| Document | Client sent a doc, or is asking about one | Info (blue) |
| Question | Client has a specific question | Primary (slate) |
| Payment | Client asking about an invoice or payment | Success (green) |
| Scheduling | Client wants a call or meeting | Warning (amber) |
| Urgent | Time-sensitive | Destructive (red) |
| FYI | No action needed — receipt, “thanks”, and the like | Muted (gray) |
| Follow-up | Continuation of an earlier thread | Warning (amber) |
Outgoing and system messages aren’t tagged. The badge always reflects the latest incoming message.
Why it matters
Triage. The Needs Action filter selects threads where the latest incoming intent is one of Document, Question, Payment, Scheduling, or Urgent. FYI flows skip past it. Awaiting Reply is filtered separately based on your outgoing activity.
If you spot a wrong tag, you can ignore it and act on what the message actually says. Assure Pro learns from how the team handles messages over time.
[Screenshot: Thread header with an intent badge]
How suggested action chips work
Below the message stream and above the compose form, Assure Pro offers up to four action chips per incoming message. Each chip is a dashed pill with a colored icon — click to act.
The five action types
| Chip | What it does |
|---|---|
| Request document | Opens the client’s documents tab pre-filled with a request dialog (see Requesting documents) |
| Schedule | Drafts a “let’s pick a time” reply via the AI Draft flow |
| Create task | Opens the workflow page with a new-task dialog pre-filled with this client and context |
| Send template | Drafts a reply via AI Draft, treating the chip label as the prompt |
| Mark resolved | Closes the conversation (with a confirmation first) |
Chips appear only when Assure Pro is confident an action is appropriate. Document intent typically yields “Request document” and “Create task”. Question yields “Send template” and “Create task”. FYI typically yields only “Mark resolved”.
How to mark a thread resolved
Click Mark resolved — a modal asks:
Close this conversation? It can be reopened later.
Confirming closes the conversation and removes it from active triage filters. The thread is still visible in All (filtered to closed) but no longer demands attention.
How to use AI Draft
The sparkle button (✦) in the compose form asks Assure Pro to draft a reply using the thread’s full context.
How to trigger a draft
Three ways:
- Click the sparkle — drafts based on the current thread plus any anchor text you’ve already typed.
- Click a “send template” or “schedule” chip — auto-fires the draft with the chip label as the prompt.
- Click it cold — when a conversation is selected, the sparkle is enabled even without text. Assure Pro uses thread context only.
The button shows “Drafting…” while it’s working (typically 2–4 seconds).
The draft card
When the draft lands, a card appears above the compose form:
┌──────────────────────────────────────────────────┐
│ ✦ AI Draft — Replying to: RE: Q2 estimates │
│ │
│ Subject: Re: Q2 estimates │
│ │
│ Hi John, the Q2 estimated payment of $4,250 │
│ is due June 15. I'll send the voucher by EOD. │
│ Let me know if you'd like ACH withdrawal set up │
│ instead. │
│ │
│ [Insert] [Regenerate] [Shorter] [More formal] │
│ [×] │
└──────────────────────────────────────────────────┘[Screenshot: AI Draft card with Insert, Regenerate, Shorter, and More formal actions]
The four draft actions
| Action | What it does |
|---|---|
| Insert | Replaces the compose body with this draft. Subject also inserted (email only). Closes the card. |
| Regenerate | Drafts again with the same context. Shows the “Refining…” state until it’s ready. |
| Shorter | Cuts the draft length roughly in half. |
| More formal | Tightens tone, removes contractions, and shifts to business-formal. |
| Discard (×) | Closes the card. The compose body stays unchanged. |
You can iterate — Regenerate, then Shorter, then Insert. Each pass starts from the previous draft, not from scratch.
What the draft uses for context
| Context | Used? |
|---|---|
| Full message history in the thread | Yes |
| Client name and entity type | Yes |
| Anchor text already typed in compose | Yes — used as a hint, not a literal start |
| Active engagement, return type, tax year | Yes (if the client has one) |
| Firm name and voice | Yes (from your firm profile and branding) |
The draft is biased to factual and brief. It doesn’t invent numbers — if the thread doesn’t mention a specific amount, the draft uses placeholders.
When the draft can’t be confident
If Assure Pro doesn’t have enough context to draft factually, the card lands as an error:
I don’t have enough context to draft a reply. Add a hint in the compose box and try again.
This is intentional. Better to fail loud than send a confident reply with made-up details.
How thread summaries work
Above the message stream, a small card:
┌────────────────────────────────────────────┐
│ Client is asking about Q2 estimated │
│ payments. Sent confirmation 3 days ago. │
│ Waiting on their bank info. │
└────────────────────────────────────────────┘When it appears
Summaries auto-generate when a thread has three or more messages. Single-message threads don’t need one.
How fresh the summary is
The summary refreshes when the thread changes. If you refresh quickly, you may see the previous version for a few seconds.
Why it matters
For tax pros juggling 40 or more clients, picking up where you left off is the bottleneck. The summary gives you a two-second context switch instead of scrolling 15 messages back. Especially handy when a client comes back mid-season with a thread from January.
When AI gets it wrong
| Symptom | What to do |
|---|---|
| Wrong intent tag | Ignore it and act on the message content. Assure Pro self-corrects over time from your team’s actions. |
| Draft has wrong specifics | Discard and type your own message. Assure Pro avoids fabrication but can still misread context. |
| Suggested action doesn’t match | Don’t click it. Chips are suggestions, not gates. |
| Summary is off | Refresh the page. If still wrong, scroll the thread directly. |
There’s no “report a bad draft” button yet. The team-feedback loop is informal — flag patterns in your weekly review.
Permissions
| Action | Who can do it |
|---|---|
| See intent badges | Anyone with permission to view communications |
| Click suggested actions | Anyone with permission to send communications |
| Use AI Draft | Anyone with permission to send communications |
| Mark a thread resolved | Anyone with permission to send communications |
Next
- Inbox & triage — the surface where intent badges show.
- Templates — when AI isn’t the right answer, save a template.
- Channels — the channel the AI Draft fills in.