Skip to content

Agent templates

An agent template is a complete starting point for a whole agent, aimed at a common use case. You pick one when you create an agent, and Anychat copies its document onto the fresh agent: Personality, Guardrails, Goals, Playbooks, and, where relevant, an Outreach and People fields.

Everything except your identity and credentials arrives pre-wired, and from there it is yours to edit.

Templates are curated by Anychat. This page covers the six shipped today.

Template What it is for
Generic Agent A blank slate you shape yourself.
Sales Development Agent Qualify a known lead and book a call with their representative.
Med Spa Concierge An inbound consumer concierge for a med spa or aesthetics clinic.
Franchise Development Agent Qualify a prospective franchisee and book a discovery call, within FTC and FDD guardrails.
Local Business Answer everyday customer questions from structured business facts.
Vacation Resort Welcome guests around a stay and answer stay questions, information only.

The New agent picker lists the templates your workspace is offered, which an Anychat operator sets. By default that is every general-release template. Ask your Anychat contact when you expect a template that is not there.

A template seeds your agent once. After creation there is no ongoing link: the agent is yours, and editing it never diverges from the template. Individual catalog pieces you import later, such as a Playbook or a Personality, do keep a back-link so you can see upstream updates, which is a separate mechanism.

Setting one up

The setup is the same whichever template you choose: create the agent and seed it from the company website, review identity and personality, fill in Things and Knowledge, connect a channel, and try it in the emulator. See Create an agent.

Each section below covers only what is specific to that template.

Generic Agent

A blank slate: a professional, friendly personality and nothing else. No Goals and no Playbooks beyond the default. It answers conversationally and grounds its answers in whatever you add to Knowledge, with no built-in outcome it drives toward.

Reach for it when your use case does not match one of the vertical templates, when you want an agent that answers questions from a body of knowledge, or when you are experimenting and want a clean start.

Set it up

  1. Create the agent on the Generic template. Importing a website is the fastest way to give it something to talk about.
  2. Personality. Set the voice that fits your brand.
  3. Goals. Name the outcome a good conversation reaches, such as a call is booked, so conversations are scored against it.
  4. Playbooks. Add one per situation you want handled. The Default Playbook is where open-ended conversations start.
  5. Capabilities. Switch on what the agent needs to act, such as Scheduling for booking. A capability that needs configuration flags it on the Capabilities page.
  6. Knowledge and Things. For an agent that mostly answers questions, this is often all you need.
  7. Connect a channel and test.

When you find yourself rebuilding the same sales or booking flow on a Generic agent, start from the Sales Development or Med Spa Concierge template instead, since both already wire those Playbooks and Scheduling together.

Sales Development Agent

Engages a human-qualified lead over rich messaging, answers their questions about your catalog, and books a call with their assigned representative. It is the reference example of a well-formed Anychat agent.

A typical conversation runs through five stages.

  1. Opening. For operator-originated outreach, the agent sends a short personalized greeting from your Outreach opener, referencing the lead's own inquiry.
  2. Discovery. It understands what the lead is trying to accomplish without re-screening an already-qualified lead.
  3. Catalog information. When they ask how something works or what it costs, it surfaces the relevant Things carousel and answers from the catalog and Sources.
  4. Scheduling. When they are ready, it offers a slot card of available times, books the appointment with the representative, and confirms with an add-to-calendar action and a tap-to-call.
  5. Escalation. When they ask for a person, it surfaces your real contact options. It never fakes a live handoff.

Preloaded: Goals for booking the call, the Sales Discovery, Provide Product Information, Schedule a Sales Call, and Escalate to Human Playbooks, an outreach opening Playbook owned by its Outreach, Scheduling, compliance Guardrails, People fields for pre-call context, and an Outreach with its opener.

Set it up

  1. Create the agent on the Sales Development template and import the company website.
  2. Representatives. On the Representatives tab of Capabilities · Scheduling, add the people the agent books calls with: name, title, phone, email. Mark one as the default. The booked call, the confirmation copy, and the tap-to-call all use this person. Left empty, the agent books against "someone from our team", which is workable for a pilot and reads worse than a named rep.
  3. Outreach. Under Build · Outreach, write the opener the agent sends when you start the conversation. Keep it short and reference the lead's own inquiry. See Outreach.
  4. People fields. The template ships with pre-call context fields such as buyer type and purchase timeline. Adjust them to what your representatives want captured. The agent fills them from the conversation, never by interrogating the lead.
  5. Things and Knowledge. Make sure every product the agent should pitch is a Thing with an accurate description, and that pricing and policy questions are covered in Sources.
  6. Guardrails. Review the claims-not-to-make list and any disclaimers your industry requires.
  7. Scheduling. By default the agent proposes business-hours times in the prospect's own time zone, resolved from the conversation or their details.
  8. Connect a channel and test an end-to-end booking.

Outreach sends over RCS. Confirmations and follow-ups happen in the messaging thread, so the agent never promises a separate email or a day-of reminder it cannot send.

Med Spa Concierge

An inbound consumer agent for a med spa, aesthetics clinic, or salon. A prospective guest texts the business, and the concierge greets them, helps them explore treatments, find the nearest location, and book a visit, grounded in the business's own catalog and Sources, and careful never to give medical advice.

A typical conversation runs through four stages.

  1. Welcome. It greets the guest and offers quick-reply chips: Explore treatments, Find a location, Book a visit.
  2. Treatments. It shows the treatment carousel and, when the guest taps one, a detail card, always framing suitability and results as something a licensed provider confirms at a consultation.
  3. Locations. It surfaces the nearest locations with addresses, hours, and a Get directions link. RCS cannot read GPS silently, so the agent asks which area is convenient.
  4. Booking. It offers a slot card, books the visit, and confirms with an add-to-calendar action and directions.

Preloaded: an Empathetic personality, medical and aesthetic claim Guardrails, Goals for booking a visit, the Concierge Welcome, Treatment Info, Find a Location, and Book a Visit Playbooks, and Scheduling. It is inbound, so there is no outreach opener.

Set it up

  1. Create the agent on the Med Spa Concierge template and import the spa's website. The treatment menu becomes your Things, and pages such as services, pricing, financing, and locations become Sources.
  2. Treatments. Review the imported Things. Give each a clear description: what it is, roughly how long it takes, what the downtime is. Detail such as aftercare or candidacy belongs in Sources rather than on the card.
  3. Locations. By default the agent draws on the locations page imported into Sources and asks which area is convenient. To have it present a fixed set of branches with addresses, hours, and directions links, add them to Knowledge.
  4. Personality. Empathetic is the default and suits sensitive, consultative topics. Adjust it when your brand voice is more upbeat.
  5. Guardrails. The medical-aesthetic guardrail keeps the agent out of diagnosing, dosing, and promising guaranteed results, and points guests to a consultation. Review it and add brand-specific disclaimers.
  6. Booking. Add a representative such as "the front desk" when you want a name and number on the confirmation. Otherwise visits are booked with "our team".
  7. Connect a channel and test the explore, locate, and book path.

No medical advice

The concierge is a front-desk helper rather than a clinician. It does not assess whether a treatment is right for someone or interpret symptoms, which is for a licensed provider at a consultation. Keep that line clear in any guardrails or Knowledge you add.

Franchise Development Agent

Engages a prospective franchisee over rich messaging: it answers questions about the opportunity and the investment, qualifies the lead against your published thresholds, and books a no-obligation intro or Discovery Day call with your franchise-development team, inside FTC Franchise Rule guardrails.

A typical conversation runs through four stages.

  1. Opening. After a prospect submits an interest form, the agent follows up, confirms they are exploring ownership rather than booking a service, and offers to cover investment, qualification, or process.
  2. The opportunity. It shares the investment snapshot and proof points as cards, grounded in your Sources, noting that figures are representative and that the FDD governs.
  3. Qualification. It asks a few fit questions covering target market, the liquid-capital and net-worth thresholds, and ownership background, without demanding financials.
  4. Booking. For a qualified lead it books an intro call with the development team and notes that the FDD will be sent beforehand.

Preloaded: the same structure as the Sales Development Agent, plus an FDD and FTC compliance guardrail and franchise-qualification People fields covering target market, liquid capital, net worth, ownership experience, and topics for the team.

Set it up

  1. Create the agent on the Franchise Development template and import the franchise website. Opportunity pages, investment ranges, and proof points become Sources and Things.
  2. Proof points. Curate the Things the agent can show: rankings, footprint, the revenue model, support. Keep claims to what your FDD and marketing support.
  3. Qualification. Review the franchise People fields and set your team's thresholds. The agent captures these conversationally to gauge mutual fit, and never accepts a deposit or negotiates fees in chat.
  4. Knowledge. Make sure the investment snapshot, what is included, the path to ownership, and any FDD Item 19 figures you cite are in Sources, so the agent quotes them accurately.
  5. Representatives and Outreach. Add the franchise-development team as the representative the call books with, and tailor the Outreach opener for a prospect who just submitted an interest form.
  6. Guardrails. Read these carefully. The FDD and FTC guardrail keeps the agent compliant: the chat is general information rather than an offer to sell a franchise, and any financial figure is representative rather than a guarantee. Extend it with your counsel's required language.
  7. Connect a channel and test a qualification-to-booking conversation.

Compliance is not optional

Franchise sales are regulated. The template's guardrail is a sensible default rather than legal advice. Have your franchise counsel review the disclaimers, thresholds, and any earnings claims before you go live.

Local Business

Answers the everyday questions customers text a storefront, restaurant, or service business: are you open right now?, where are you?, do you allow pets?, how do I reach someone?

It answers from the agent's business info, covering address, weekly and holiday hours, amenities, and price range, plus Sources. It connects people to your real contact channels and declines gracefully when the facts do not cover a question rather than guessing.

The open-right-now answer is computed by the platform from your stored hours and time zone, including overnight windows and holiday overrides, so it always agrees with what you published.

Set it up

  1. Create the agent on the Local Business template and import the business website. The import fills business info from the site's structured data and pages, alongside identity, Things, and Sources. Any FAQ page it finds becomes Facts.
  2. Business info. Review what arrived and fill the gaps. Confirm the timezone, since every stored time is read in it and the open-right-now answer needs it. Check the weekly hours, and add holiday special hours and the amenities customers ask about.
  3. Connect a channel and test the hours, location, and amenity questions, including one the facts do not cover, to see the graceful decline.

Vacation Resort

A guest assistant for a resort or hotel. It sends three messages the resort triggers around a stay and answers guest questions in between, from the resort's Facts and Sources.

It is information only. It never books, changes, or reserves anything. When a guest asks for something that needs action, such as a dinner reservation, a late check-out, or a question about the bill, the agent says it cannot arrange that here and points to the front desk in person or to the phone and email on the agent's identity.

The three stay messages are Outreaches, each with a reviewed opener, its own Playbook, and its class set to Service, so the marketing frequency cap never holds them back.

Outreach When the resort sends it What follows the opener
Pre-arrival Welcome A day or so before check-in One line offering the before-you-arrive FAQs as quick replies: check-in time, directions and parking, what to pack, dining.
Check-in Orientation On arrival One line offering an orientation to the main amenities as quick replies: Wi-Fi, dining, pool and spa, activities, front desk.
Check-out Thank You On departure day At most one line pointing departure questions to the front desk.

Between those, the Guest Questions Playbook answers from Knowledge, and Reach the Resort hands any request for action or a person to the resort's listed contact options. The agent never says a request was passed along or that someone will follow up in the thread.

Set it up

  1. Create the agent on the Vacation Resort template and import the resort website. Amenities, dining, policies, and any FAQ page become Knowledge, and the identity fills from the site.
  2. Contact details. Confirm the phone and email on Identity. These are the only contact options the agent gives, so make the phone the number a guest should call to reach the front desk. Use Availability to say when the desk is staffed.
  3. Knowledge. Cover what guests text about: check-in and check-out times, Wi-Fi, parking, pool and spa hours, dining hours and dress code, activities, pet and smoking policies, directions. Anything not covered gets a plain "I'm not sure" and the front desk.
  4. Message templates. On Build · Behavior · Message Templates, edit the three stay openers to match your voice. Each fills the guest's first name and the resort name from the Person record and identity.
  5. Send a stay message from the guest's record. Press Send, choose the Outreach for the moment, check the rendered opener, and send. Your property system can ask for the same thing through the API.
  6. Connect a channel and test a stay: send the pre-arrival message, ask a question, then ask for a dinner reservation to see the handoff.

No actions on the guest's behalf

The template ships without scheduling, People fields, or custom integrations. Adding a capability later does not change the guardrails, which tell the agent it cannot act for a guest. Revise them when you give the agent something it can do.

What's next