Inbound & qualification

Route leads and book meetings

Help each enquiry reach the right person and a meeting that has a clear purpose.

Copies a prompt for your AI assistant

View prompt

Start wherever you are

Bring a routing problem or an existing process. Your agent helps you work through ownership and the next step.

Start with your AI assistant. Connect tools when needed.

Fictional example

You

Inbound demo requests land with me, even when someone else should take them.

Agent

How would you decide who is best placed to help?

You

Lena handles agencies and Omar handles in-house teams. We need a fallback when either is unavailable.

One possible routing plan after exploring ownership, availability, and exceptions together

Proposed route · fallback not yet agreed

Clear owners. One fallback to decide.

For this fictional agency request, Lena is the proposed owner. Check availability before making a promise to the prospect.

Primary route: Agency enquiry → Lena, provided she can take it. In-house team enquiry → Omar, under the same condition.
Proposed fallback: Keep unclear requests with the current coordinator for review, if you choose this fallback. Do not silently assign them to an unavailable owner.
Before offering a meeting: Confirm the purpose, owner, duration, time zone, and actual available times through an authorized source.

Agreed in this example

The team has chosen Lena for agencies and Omar for in-house teams. A fallback owner has not been agreed.

Still to check

The fallback choice, Lena’s capacity and calendar, the prospect’s time zone, and whether a meeting is the useful next step.

A next step to resolve

Choose the fallback owner, then check Lena’s availability before offering times or applying the exception path.

Context & open questions

Existing ownership: Check whether this person or company already has an owner before applying a new routing rule.
Meeting status: Suggested times, an invitation sent, and a meeting accepted are different states. Verify and report the actual one.
Status: Plan only. No assignment changed, calendar accessed, invitation sent, or meeting booked.

Your result will reflect your conversation. Keep it in your assistant or a document you choose.

How the tools fit together

01
Enquiry & context
Who needs help, and any existing relationship.
02
Ownership decision
Agreed rules, capacity, and exceptions.
03
Availability · if needed
An authorized calendar or scheduling tool.
04
Verified next step
Report assignment and meeting status separately.

Choose tools together. Execution depends on the connections and actions available in your assistant.

Read the full guide

Start wherever you are

Start with one enquiry or a routing problem. You can work out the rules before connecting tools.

Figure it out together

Choose what determines ownership
Discuss customer needs, existing relationships, team responsibilities, and capacity.
Handle the exceptions
Decide what should happen when information is missing, ownership conflicts, or someone is unavailable.
Arrange the right next step
Agree the meeting purpose and details, check real availability, and distinguish an offer from a confirmed booking.

Tools and connections

Your AI assistant: Coach the routing choices and prepare a reviewable rule.
Capable · optional: Check available lead, company, and ownership context; use assignment operations only if supported.
Calendar or scheduling tool · optional: Check authorized availability and use supported scheduling actions if you choose.

What you’ll keep

A useful result and a copyable working brief with your decisions, reasons, evidence, assumptions, actual status, pending actions, and next question. Bring it back when you’re ready to continue.

A useful first outcome

You have clear ownership rules, an exception path, and an honest status for the next meeting step.

When to revisit it

When responsibilities, capacity, existing ownership, or meeting preferences change.

View the setup prompt

Copy into your AI assistant to begin

Help me route inbound leads and arrange useful meetings through a guided conversation. Help me work out ownership, capacity, exceptions, and the appropriate next step without assuming every enquiry needs a meeting.

Check the context I have already supplied first. If I have not described the situation, ask: "Where do incoming enquiries get stuck today?" If I have already answered that, acknowledge it and ask the next useful unanswered question. Reuse existing routing rules, team decisions, or a working brief, check what has changed where relevant, and start with my named concern. I do not need connected calendars or a complete routing policy to begin.

Ask one useful question at a time and explore only relevant gaps. Understand what would make an owner appropriate: the person's needs, account or lead ownership already in place, team responsibilities, expertise, territory where relevant, and real capacity. Do not invent routing criteria or assume round-robin assignment is the best approach. Offer practical options and tradeoffs if I am unsure.

Help me choose a simple rule and an exception path. Ask what should happen when information is missing, multiple people could own the enquiry, an account already has an owner, or the intended person is unavailable. Do not silently overwrite existing ownership. Make fallback responsibility explicit without inventing a shared queue or workflow that the chosen tool does not support. Draft a small routing table or a decision for one example early so we can refine it together.

Before proposing a meeting, establish whether it would help and what it should accomplish. Reuse agreed details and ask only for missing constraints such as the right participants, duration, time zones, scheduling preferences, or buffers. Do not infer availability from working hours or a past calendar view. Use a calendar or scheduling service only within the source and action scope I choose. Check current availability at the point required by the supported scheduling operation, and handle conflicts or partial failures openly.

Keep ownership and meeting status separate. Proposed owner, assignment written, times offered, invitation created or sent, and attendee acceptance are different facts. Verify the actual tool result and do not say "booked" or "confirmed" if the evidence only supports an invitation or a suggested time. Do not contact people, reassign records, or reserve time solely because a routing plan exists. Review unresolved decisions and the proposed action with me, then use the specific authorization already provided.

Keep a reusable working brief as we decide things. Include our goal and scope; the decisions and why we made them; the exact current output; sources and evidence; assumptions and open questions; the actual status of any actions; pending work; and the next useful coaching question. Add owners, dates, and a review point only where we agreed them. Distinguish a proposed action from an authorized action, an attempted action, and a verified result. Give me an early provisional result when the context supports it, then improve it with my feedback rather than waiting for every detail.

Before using connected tools, ask which sources I want to use unless I have already specified them. Work only within that scope. Use Capable for available context and supported records or operations; check the actual tools, fields, permissions, and capabilities instead of assuming an integration can read, write, send, schedule, or store anything. Use existing authorization for the exact action it covers. Resolve missing authorization or consequential choices before acting, without making me repeat settled decisions. Report what actually happened and any partial failures; do not imply that a draft, copied prompt, or configured rule ran successfully.

Keep the brief in this conversation unless I choose another place. Save it only if I ask and an appropriate operation is available. Do not imply that Capable or a new chat will automatically remember it. Include this continuation instruction with the brief: check what has changed, reuse the decisions that still apply, and ask the next useful question. The brief supplies context, not permission to contact people or change records. Before we pause, give me a clean, copyable version so I can continue in my chosen assistant or document.

How did it go? Optional feedback

Route leads and book meetings

Start wherever you are

Clear owners. One fallback to decide.

Agreed in this example

Still to check

A next step to resolve

Example working brief

Enquiry & context

Ownership decision

Availability · if needed

Verified next step

Start wherever you are

Figure it out together

Tools and connections

What you’ll keep

A useful first outcome

When to revisit it