Working with it over email
Email is the whole interface. Ask a question, send a file, or request something — and reply to keep the conversation going.
Everything happens over email. To get started, just email your Agent's address (the one our team set you up with) — or reply to any email it sends you. It remembers the conversation, so you can go back and forth naturally.
Ask it questions
Ask about what's in your Knowledge Base or what your team has been asking:
"What are people asking about time off lately?"
"What does our Knowledge Base say about the dress code?"
It answers from your content and activity. If the answer isn't there, it'll say so plainly — "I don't have that in the Knowledge Base" — instead of guessing. That's on purpose: a confident wrong answer is worse than an honest "I don't know."
Ask how busy it's been
Ask for activity over any period up to 30 days:
"How many people used it last week?"
"How many conversations did we have over the past 30 days?"
You get the number of workers who were actually active, the number of
conversations, and the average per person. Leave the dates out and you get the
last 7 days. The window is a rolling one — "the past 30 days" means the last 30
days ending now, not last calendar month.
If it can't see the whole period it will tell you so and give the figures as
"at least N" rather than quietly rounding down.
Ask what it's failing to answer
This is the one worth asking regularly, because it tells you what to write next:
"What did it not answer last week?"
"What got a thumbs down?"
You get the kinds of question it's missing — grouped into themes with a
count each — so you can see what's worth adding to the Knowledge Base first.
Worth knowing what "didn't answer" means here: your people always got a reply.
These are the ones where the reply didn't draw on anything you'd given it, so
the Agent answered from general knowledge instead of your content. That's the
gap you can close. The other kind, thumbs-down, covers answers a worker
marked unhelpful.
You'll never see the questions themselves — only the themes. Workers are told
their individual messages stay confidential, and that holds here. On a very
quiet Agent it may say there wasn't enough activity to describe the topics
safely; that is not the same as "no gaps".
Ask it to draft things
It can draft announcements, summaries, and similar. Drafts come back clearly marked "DRAFT — please verify," usually as an attachment you can edit. Always give a draft a read before you use it — it's a starting point, not a final answer.
Tips for good results
- One thing at a time works best. A clear, single request gets a clear reply.
- Reply in-thread to continue — it keeps the context.
- Be specific about locations, roles, or dates when they matter.
What it can do for you
| You want to… | Just ask it to… |
|---|---|
| Add a document to the Knowledge Base | Attach the file and say "add this" — see Adding knowledge |
| Send an alert to your whole team | Describe it — see Alerts |
| Message specific people or a group | Describe who + what — see Messages |
| Get something that needs a person | Ask — see Getting help |
| Understand recent activity | Ask about questions, trends, or gaps |
| See how many people are using it | Ask for usage over any window up to 30 days |
| Find out what it's failing to answer | Ask what went unanswered, or what got a thumbs down |
| See which documents actually get used | Ask for the content report — see Your Content Analysis Report |
| Clean out stale Knowledge Base content | Name the files (or attach a list) — our team handles every removal |
Every reply is a chance to discover something new it can do — when in doubt, just ask.
Updated about 1 month ago