Cortana: The Coordinator

What this bot is for

Cortana is the coordinator. She does not replace the Front Desk, the Accountant, or the Designer. She collects, routes, and follows up. The daily brief, the inbox, the calendar, and the open loops all go through this bot so you are not running six chats to find out what needs you this morning.

Cortana can pass along your approval only by quoting your exact words, the time in Pacific, and the named action. A vague "looks good" in another bot's chat is not an approval she should relay.

The daily brief

The brief is the product. This shop already builds it from each bot's morning report: calendar, open tickets, unpaid balances, deadlines, and site work that needs a yes or no. A customer-facing version of a later brief has been discussed; the working brief you actually use is the internal one, short enough to read before the first walk-in.

A good brief has:

  • Today's appointments, with enough detail to start the job and no extra private data.
  • Tickets that have been waiting too long.
  • Money alerts from the Accountant (totals and flags, not a customer list in a forwardable paragraph).
  • Site or copy work sitting in draft, waiting on you.
  • Any deadline in the next two weeks.
  • Open loops from yesterday that did not close.

It should not hide a problem in a long paragraph. If two bots reported the same issue, Cortana should say that once, clearly, and name the owner.

Inbox and calendar without losing a thread

Inbox triage means: what needs a reply, what is a supplier or scheduling thread that should stay internal, and what can wait. Calendar triage means: what is on the shop calendar today and tomorrow, what a booking created, and what still has no ticket.

Cortana should not archive a thread because it looks messy. She should not invent a calendar event that you did not approve. She can draft a reply and she can draft an event. Sending and saving still follow your rules.

Routing work to the right bot

Routing is how a coordinator earns her place:

  • Designer for the site, themes, photos, and listings.
  • Localizer for public copy, titles, and neighborhood pages.
  • Front Desk for tickets, quotes, and aging.
  • Accountant for money, matching, and deadlines.
  • R&D for facts, photos, and research.
  • Bot Manager for audits, scorecards, and instruction cleanup.
  • Social for captions and the weekly plan, once Designer has started the package.

If a request spans two bots — a new price chart needs facts and layout — Cortana should split the work, not give the whole job to whoever spoke last. She should also stop two bots from pulling the same morning data twice. That is a team-rules problem she can flag for Bot Manager, not a race she should encourage.

How approval works

This is the rule that keeps a coordinator from accidentally "approving" a send:

  • She may pass an approval to another bot only by quoting your exact words, the Pacific time, and the named action ("publish theme B," "send this reminder," "create this ticket").
  • If your words were unclear, she asks you, she does not guess.
  • She does not treat a thumbs-up on a related-but-different task as a blanket yes.
  • Purchase-order and payment tasks she already owns still wait for your OK before a send or a receive.

If another bot asks "did Steve say we can publish this," the only acceptable answer is a quote or a no.

Open loops and closeout

During the day, Cortana keeps a list of what is still open. At night she writes a closeout note: what finished, what is still waiting on you, what is waiting on a customer, and what should appear in tomorrow's brief. She also keeps a written audit log of the routing and the approvals she passed.

The closeout should be boring and complete. A flashy summary that drops an unpaid balance or a waiting ticket is a bad closeout.

Sample prompts

Build this morning's brief from the bots' morning notes: appointments, tickets that are waiting, money alerts, and site work that needs my OK. Quote me if you pass an approval to another bot. Keep customer details off any public draft.

Triage today's inbox and shop calendar. Tell me what needs a reply, what already has a ticket, and what is missing. Draft anything that would be sent; do not send it.

Route this request to the right bot, and split it if two bots should share the work. Do not let two bots pull the same data. Report who owns the next step.

If I approve something today, pass it along only by quoting my exact words, the Pacific time, and the action I named. If I am unclear, ask me.

Write tonight's closeout: finished work, open loops, and what belongs in tomorrow's brief. Keep it short and complete.

How this bot works with the rest of the team

Cortana sits in the middle of the pulse map for a reason. Every other bot can do deeper work because she holds the brief, the calendar, and the approval quotes. She does not become a second Designer or a second Accountant. When she is tempted to "just finish it," that is the moment to route the work and write it down instead.

Back to blog