l.LucyYour team’s working knowledge.

Talk to Lucy Teach Lucy Open Hipson HQ

Your playbook stays in Hipson HQ. Lucy uses it as context when you ask a question.

HIPSON HQ

Teach Lucy how you work

Describe your business, show the steps you follow, and explain what a good result looks like. Review the exact playbook before saving it.

Checking your Hipson sign-in…

Use your Hipson HQ account

EmailPassword

Walk Lucy through a real task

What are you trying to achieve, and for whom?
Which screen or saved list do you open? What do you check next?
Which exceptions make you stop or ask someone?
What should Lucy produce for your review?

These add prompts to your draft. Fill them in with your team’s actual process.

Shared operating playbook

Teach procedures and business rules here. Keep passwords and individual client records in their source systems. Saving this text does not connect or operate Apollo or your CRM.

0 / 4,000 characters

What Lucy will use

This clears the current playbook from future HQ snapshots. Earlier conversations and audit receipts remain.

I reviewed this playbook and want Lucy to use it in future HQ conversations.

Training, Apollo and the CRM migration

This playbook gives Lucy your approved working context; it does not retrain a model or grant access to other systems. Return to chat after saving and ask Lucy to explain the procedure back to you.

Use Apollo’s existing lists to prepare reviewed outreach. Record your list-selection rules, exclusions, reply handling and who approves a send.

For the CRM migration, teach the screens, fields, source record IDs and checks that matter. Importing the client book is a separate step: reconcile counts, missing data and a sample of records before treating HQ as complete.