> ## Documentation Index
> Fetch the complete documentation index at: https://docs.hiveku.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Using the Sales Co-pilot

> Daily workflow with the AI Sales Co-pilot

This is the day-to-day playbook for working with your AI Sales Co-pilot. It covers where to find it, how to ask questions, how to use meeting transcripts, and how to lean on calendar awareness for prep.

## Where it lives

<CardGroup cols={2}>
  <Card title="Quick-ask pill" icon="bolt">
    `/dashboard/crm/` — a small pill labeled "Ask AI Co-pilot" in the top bar.
  </Card>

  <Card title="Dedicated chat" icon="comments">
    `/dashboard/crm/memory/` — full conversation, pending actions, and history.
  </Card>

  <Card title="Inline on records" icon="address-card">
    Every contact and deal page has a "Co-pilot" sidebar with suggestions.
  </Card>

  <Card title="Profile settings" icon="user-gear">
    Settings > Profile — set your email signature so drafts sign off as you.
  </Card>
</CardGroup>

## The quick-ask pill

The pill is a fast in-and-out interface. Click it, type a question, hit Enter, get an answer or a staged action. Use cases:

* "What deals are at risk this month?"
* "Draft a follow-up to Acme Corp"
* "Summarize my meeting with Sarah yesterday"
* "What's the next step on the Northwind deal?"
* "Find all contacts at companies over 200 employees that haven't replied in a week"

The pill is great for short tasks. For multi-turn conversations, jump to the dedicated chat at `/dashboard/crm/memory/`.

## The chat interface

The full chat at `/dashboard/crm/memory/` keeps history across days, supports multi-turn refinement, and has tabs for pending actions and configuration.

<Steps>
  <Step title="Open the chat">
    Click "Memory & Co-pilot" in the CRM sidebar.
  </Step>

  <Step title="Start a conversation">
    Type a question. The Co-pilot has access to your CRM, calendar, email, and call records.
  </Step>

  <Step title="Refine">
    "Make the email shorter." "Use a more casual tone." "Add a P.S. about the new feature."
  </Step>

  <Step title="Approve actions">
    When the Co-pilot proposes something with side effects (sending email, updating CRM), it goes to the pending queue. Approve from there.
  </Step>
</Steps>

## Asking good questions

The Co-pilot is best when you're specific about what you want. A few patterns that work well:

<Tabs>
  <Tab title="Status questions">
    * "What deals are stalled?"
    * "Who haven't I followed up with this week?"
    * "Which prospects opened my emails but didn't reply?"
    * "What meetings do I have tomorrow and what should I know?"
  </Tab>

  <Tab title="Drafting">
    * "Draft a cold email to Sarah at Acme — they're a 50-person SaaS, might benefit from our analytics"
    * "Reply to Bob's pricing question — keep it under 100 words"
    * "Write a follow-up after my demo with Northwind, summarize the agenda we discussed"
  </Tab>

  <Tab title="Summarizing">
    * "Summarize my call with Northwind"
    * "What did we agree to in the last 3 meetings with Acme?"
    * "Pull out the action items from yesterday's discovery call"
  </Tab>

  <Tab title="Suggestions">
    * "What's the best next step on the Globex deal?"
    * "Should I push for a close this week or wait?"
    * "Who in my pipeline looks like a good fit for the new pricing tier?"
  </Tab>
</Tabs>

## Reading meeting transcripts

After every call (Zoom, Google Meet, Teams, or your phone system if recorded), the Co-pilot ingests the transcript and produces:

* A short summary
* A list of explicit commitments ("I'll send pricing by Friday")
* Action items as draft tasks in your CRM
* Sentiment notes (interested, hesitant, blocking concerns)
* Suggested follow-up email

<Steps>
  <Step title="Find the transcript">
    On the contact or deal page, the meeting appears in the activity timeline with a "Transcript" link.
  </Step>

  <Step title="Read the summary">
    The Co-pilot's summary appears at the top — usually 4-6 bullets. Skim it before opening the full transcript.
  </Step>

  <Step title="Approve action items">
    Action items show up in the pending queue. Approve to convert into CRM tasks.
  </Step>

  <Step title="Approve the follow-up">
    The drafted follow-up email is also in the queue. Edit if needed, approve to send.
  </Step>
</Steps>

<Tip>
  Have the Co-pilot create the action items even when you'll do them yourself. Tasks land on the right contact/deal, with deadlines, and you have a clean ledger of what was promised.
</Tip>

## Calendar awareness — meeting prep

Before every booked meeting, the Co-pilot generates a brief. You'll see it 1-24 hours before the call (configurable) on:

* The dedicated chat page
* A Slack DM (if Slack is connected)
* An email reminder (if enabled)

The brief contains:

* **Who** — name, role, company, prior interactions
* **History** — past meetings, emails, deals, notes
* **Last activity** — what they did most recently in your funnel
* **Likely topics** — based on prior conversations and where the deal stands
* **Suggested questions** — open-ended prompts to advance the deal

<Info>
  Briefs are most useful when you have rich CRM data on the contact. New, sparsely-detailed contacts get briefer briefs. Add notes after each call — the Co-pilot uses them to deepen future briefs.
</Info>

## CRM activity awareness

The Co-pilot watches CRM activity and surfaces patterns:

* **Deals stuck**: "Globex hasn't moved in 3 weeks" — proposes next step
* **Missed promises**: "You said you'd send pricing to Sarah Wednesday — it's Friday" — drafts the email
* **Aging tasks**: "These 6 tasks are past due" — proposes deferring or completing
* **Re-engagement opportunities**: "Bob opened your last email 4 times but didn't reply" — drafts a check-in

These appear as nudges on the dashboard or as items in the pending queue.

## Email signature

The Co-pilot drafts emails that sign off as you. Set your signature in Settings > Profile so its drafts include the right name, title, phone, and any links you want.

```
Sarah Jones
Account Executive · Acme
sarah@acme.com · (415) 555-0100
```

<Warning>
  Without a signature configured, drafts will use a generic sign-off. Worth taking 30 seconds to set this up before approving any outbound drafts.
</Warning>

## Tone matching

Over time the Co-pilot learns your voice from drafts you approve and edits you make. The first few weeks may need more editing; after that, drafts get noticeably closer to how you'd naturally write.

You can also explicitly steer tone with skills/rules:

* "Use casual lowercase greetings ('hey alex' not 'Hi Alex')"
* "Never use exclamation points in cold outreach"
* "Sign off with 'Cheers' rather than 'Best'"

## Privacy and access

The Co-pilot only sees what you've connected: your CRM, your connected calendar(s), your connected email account(s), your phone records. It does **not** see other users' private data without explicit team-share, and never sees data outside your Hiveku account.

## Next steps

<CardGroup cols={2}>
  <Card title="Pending actions" icon="list-check" href="/sales/pending-actions">
    Approve, edit, reject, and configure auto-approve.
  </Card>

  <Card title="Skills and rules" icon="book" href="/ai/skills-rules">
    Teach the Co-pilot how your team works.
  </Card>
</CardGroup>