> ## 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.

# Enable the Sales AI Co-pilot

> Turn on the Co-pilot, connect calendar, set signature, train preferences

This guide walks through first-time setup for the Sales AI Co-pilot — turning it on, giving it the context it needs, and approving a first batch of pending actions to teach it your preferences. Plan for 15-20 minutes.

## Before you start

You should have:

* A Hiveku account with CRM access
* A Google or Outlook calendar to connect (so the Co-pilot can read meetings)
* A Gmail or Outlook email account connected (so it can read email threads), or your sending set up via Hiveku Email
* Approval-mindset — the first week, you'll review more drafts than usual to teach it your style

## Step 1: Turn the agent on

<Steps>
  <Step title="Open the Co-pilot page">
    `/dashboard/crm/memory/`.
  </Step>

  <Step title="Toggle the agent on">
    Top-right of the page. The agent is off by default for new accounts.
  </Step>

  <Step title="Set the cost cap">
    Pick a session cost cap (default \$5/day per user). This is a safety net — set it higher later if you find you're hitting it on legitimate usage.
  </Step>
</Steps>

## Step 2: Connect your calendar

The Co-pilot uses calendar data to prep you before each meeting. Without a calendar connection, it can't surface meeting-aware insights.

<Steps>
  <Step title="Go to Settings > Integrations">
    Find Google Calendar or Outlook.
  </Step>

  <Step title="Connect">
    OAuth into the account that has your work calendar. Grant read access at minimum.
  </Step>

  <Step title="Pick which calendars to sync">
    At minimum your primary work calendar. Personal calendars are optional — useful for blocking availability but the Co-pilot will respect privacy.
  </Step>
</Steps>

For more, see [Connect Google Calendar](/how-tos/connect-google-calendar) or [Connect Outlook](/how-tos/connect-outlook).

## Step 3: Connect your email

The Co-pilot needs to read your sent and received email to draft accurate replies. Two paths:

<Tabs>
  <Tab title="Gmail / Outlook (most common)">
    From Settings > Integrations, connect your Google or Microsoft email. The Co-pilot reads your inbox and sent items, and drafts go out from your existing address. Best when you're already living in a third-party email client.
  </Tab>

  <Tab title="Hiveku Email">
    If you use Hiveku Email for sending, the Co-pilot already has access to outbound. Inbound requires forwarding inbound replies into Hiveku — see [Email setup](/email/overview).
  </Tab>
</Tabs>

## Step 4: Set your email signature

Drafts will sign off as you. Without a signature configured, drafts use a generic placeholder.

<Steps>
  <Step title="Open Settings > Profile">
    Find the Email Signature section.
  </Step>

  <Step title="Paste your signature">
    Standard format:

    ```
    Sarah Jones
    Account Executive · Acme
    sarah@acme.com · (415) 555-0100
    Schedule a call: book.hiveku.com/sarah-jones
    ```
  </Step>

  <Step title="Save">
    Drafts from the Co-pilot will use this signature going forward.
  </Step>
</Steps>

<Tip>
  Include your booking link in the signature. Many of the Co-pilot's outbound drafts naturally end with "let me know a good time" — the booking link gives the prospect a clean conversion path.
</Tip>

## Step 5: Add baseline skills and rules

Skills and rules teach the Co-pilot how your team works. Even three or four entries make a meaningful difference in draft quality.

<Steps>
  <Step title="Open Skills & Rules">
    On the Co-pilot page, navigate to the Skills & Rules tab.
  </Step>

  <Step title="Add starter rules">
    A few that work for most teams:

    * "Always include our 30-day money-back guarantee in cold replies"
    * "Don't propose discounts above 15% — those need approval"
    * "Use casual lowercase greetings ('hey alex' not 'Hi Alex')"
    * "Sign off with 'Cheers' rather than 'Best'"
    * "If a prospect mentions HIPAA, route to the enterprise team"
  </Step>

  <Step title="Save">
    Rules apply immediately to all future drafts.
  </Step>
</Steps>

For the full skills/rules system, see [Skills, Rules, and Memory](/ai/skills-rules).

## Step 6: Approve a first batch of pending actions

This is where the Co-pilot learns your preferences fastest. Spend 15 minutes reviewing your first day's queue, with thoughtful approvals, edits, and rejections.

<Steps>
  <Step title="Open the Pending Actions tab">
    `/dashboard/crm/memory/` > Pending Actions.
  </Step>

  <Step title="Review each item">
    Read the proposed action. Imagine it landing without your review — would you be happy?
  </Step>

  <Step title="Approve, edit, or reject">
    * **Approve** the ones that are dead-on
    * **Edit** the ones that have the right idea but need tweaking
    * **Reject** the ones that miss — and add a reason ("too pushy", "wrong recipient")
  </Step>

  <Step title="Resist bulk-approving">
    The first batch is your teaching opportunity. Bulk-approve in a week, after the Co-pilot has learned.
  </Step>
</Steps>

For the full queue mechanics, see [Pending Actions](/sales/pending-actions).

## Step 7: Configure auto-approve (later)

Once you trust the Co-pilot on certain low-risk action types, configure auto-approve to remove the friction.

<Steps>
  <Step title="Wait at least a week">
    Let the Co-pilot learn from your first week of approvals/rejections.
  </Step>

  <Step title="Open Auto-Approve settings">
    On the Co-pilot page > Settings > Auto-Approve.
  </Step>

  <Step title="Enable safe categories">
    Common starting set:

    * Adding tags to contacts
    * Updating lead-score
    * Creating tasks (with due date up to 7 days out)
    * Appending notes to records
  </Step>

  <Step title="Never auto-approve sends">
    Outbound emails and SMS should stay in the queue. Same for deal-stage moves and sequence enrollments — those impact forecasting and customer experience.
  </Step>
</Steps>

## Step 8: Set up notifications

You don't need to live in the queue all day. Configure notifications:

<Tabs>
  <Tab title="Slack DM">
    Connect Slack in Settings > Integrations. The Co-pilot will DM you for high-priority items (e.g., reply drafts to inbound prospect emails).
  </Tab>

  <Tab title="Email digest">
    Daily or weekly summary of pending items. Good for non-urgent review.
  </Tab>

  <Tab title="In-dashboard badge">
    Always-on badge with pending count. Default.
  </Tab>

  <Tab title="Mobile push">
    Via the Hiveku iOS/Android app. Useful for same-day responses to time-sensitive items.
  </Tab>
</Tabs>

## What to expect in the first week

* **Day 1**: Lots of pending actions. The Co-pilot is processing your CRM history for the first time.
* **Day 2-3**: Drafts are \~70% on the mark. You'll edit a lot.
* **Day 4-7**: Drafts are \~85% on the mark. Edits are mostly small tweaks.
* **Week 2+**: Drafts are noticeably in your voice. Bulk-approval starts to feel safe for low-risk categories.

## Common first-week issues

<AccordionGroup>
  <Accordion title="Too many drafts in the queue">
    Reduce the Co-pilot's "drafting verbosity" in settings. Or add rules narrowing what it should draft for ("Don't draft replies to no-reply addresses", "Skip cold outreach acknowledgments").
  </Accordion>

  <Accordion title="Drafts don't sound like me">
    Make sure your email signature is set, and add a few "tone" rules: "Use sentence-case subject lines", "Avoid corporate jargon", "Keep replies under 100 words". The Co-pilot also learns from your actual sent email — give it a few weeks to drift toward your voice.
  </Accordion>

  <Accordion title="Co-pilot isn't surfacing meeting briefs">
    Confirm calendar is connected (Settings > Integrations), and the meetings have at least 24 hours' notice. Briefs generate \~24 hours before each meeting and again \~1 hour before.
  </Accordion>

  <Accordion title="Cost cap hits before noon">
    Either you have a heavy workload (raise the cap) or you have unintended high-frequency drafts (add rules to slim them down). Check the cost breakdown in Billing to see which actions are driving spend.
  </Accordion>
</AccordionGroup>

## Next steps

<CardGroup cols={2}>
  <Card title="Using the Co-pilot" icon="comments" href="/sales/using-co-pilot">
    Day-to-day workflow.
  </Card>

  <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>