Always-On Agents

Always-On Agents.
Every Channel. Every Role.

Your AI employees answer every call, chat, and text — 24 hours a day, in the voice of the right person for that moment. Reese picks up the front desk. Vance answers the sales line. Sage handles support tickets. Nobody goes to voicemail.

Hire an Always-On Agent →
The Problem

Every unanswered call is a decision. Someone made it for you.

Lead response research shows that contacting a prospect within 5 minutes of their inquiry produces a 21× higher conversion rate than responding within 30 minutes. After-hours, that window closes completely. Every call that hits voicemail is a lead that already has a second tab open.

The problem isn't that you don't have a receptionist. It's that your receptionist works 9-to-5 and can only be in one conversation at once. When a prospect calls on Saturday at 7pm, they're not calling back Monday.They're calling your competitor.

Channels

Every way a customer can reach you. Covered.

01

Voice

  • Answers inbound calls in real time
  • Books appointments while on the call
  • Warms transfers to humans when escalation is needed
02

Chat

  • Embeds on any page via a single script tag
  • Routes to the right employee based on the page it's on
  • Handles FAQs, qualifies leads, and creates CRM records
03

SMS

  • Responds to inbound texts within seconds
  • Follows TCPA-compliant opt-out handling
  • Threads into the same contact timeline as voice and chat
04

Email

  • Classifies inbound emails by intent
  • Routes to the right department automatically
  • Drafts a reply for human review or sends directly at your discretion
Roles & Departments

The right employee answers. Every time.

A reception desk handles one call at a time. Your AI org chart handles all of them simultaneously — each routed to the employee who knows that channel.

01Receptionist

Front desk / Receptionist

→ Answered by Reese

Main number, homepage chat, default SMS

Hire Reese →
02Sales

Inbound SDR / Lead qualification

→ Answered by Vance

/pricing page, /contact, demo-request widgets

See Sales →
03Support

Tier-1 Support / Helpdesk

→ Answered by Sage

/help, docs pages, support email/SMS

See Support →
04Support

Customer Success / Renewals

→ Answered by Echo

Account portal, post-onboarding

See Support →
05Receptionist

Booking / Appointments

→ Answered by Reese

Booking pages, service-line numbers

Hire Reese →
06Receptionist

Concierge / VIP

→ Answered by Reese (multilingual)

Premium-tier numbers, page-specific widgets

Hire Reese →
07Sales

Order / Quote Intake

→ Answered by Vance

Quote forms, restaurant POS lines

See Sales →
08Receptionist + Sales

Real estate listing inquiries

→ Answered by Reese → Vance hand-off

Listing page widgets, MLS-tied numbers

See this setup →
09[ROADMAP]

Internal IT Helpdesk

→ Department: Operations

Internal portal

Coming soon
10[ROADMAP]

Recruiting Screener

→ Department: HR

Careers page

Coming soon
How It Works

From first contact to department action in four steps.

Not a phone tree. Not a chatbot script. A named AI employee who knows their department, their persona, and your business — answering on every channel.

01
Arrive

A visitor calls, chats, or texts

On any channel — a call to your main number, a widget load on your pricing page, an inbound SMS — the right employee answers. Which employee depends on where the contact arrived: homepage chat defaults to Reese; the /pricing page widget routes to Vance; your support line routes to Sage. The routing is set once when you embed the widget or configure the phone number.

02
Answer

The agent answers in role-specific persona

The voice runtime loads the employee's full persona — name, title, personality, department knowledge, and the specific instructions you've configured (“always ask for the caller's email before routing”). On voice, you hear Reese. On chat, you see Reese's name in the widget. The caller never knows they're talking to the same underlying platform Vance uses to qualify leads.

03
Act

The agent does the work inline

Books a slot on your calendar. Qualifies a lead against your ICP criteria. Creates a support ticket. Answers the FAQ without escalating. The agent isn't scripted — it has access to your knowledge base, your calendar, and your CRM. If it can handle the interaction end-to-end, it does. If it can't, it escalates with full context.

04
Hand Off

The outcome lands on the right department's board

A booked appointment creates a task on the Receptionist department's kanban. A qualified lead creates a CRM record and a Sales department task assigned to Vance. A support ticket lands in Support. The conversation happened on a phone; the work landed in the right place. Nothing falls into a voicemail inbox that nobody checks.

Per-Page Routing

One platform. A different employee on every page.

◆ Widget routing examples
Page: /pricing
Widget param: ?employee=vance
Visitor chats with Vance (Sales), not Reese
Page: /docs
Widget param: ?employee=sage
Visitor chats with Sage (Support)
Page: /contact
(no param — org default)
Visitor chats with Reese (Receptionist)

The widget embed is one <script> tag on your site. The ?employeequery parameter is optional — if omitted, it defaults to your org's Receptionist (Reese). Add it to any page where you want a specialist to answer: your pricing page gets Vance, your docs get Sage, your account portal gets Echo. One platform. Zero context-switching.

Try It

Talk to an Always-On Agent right now.

This is the actual platform widget, not a mock. Reese is answering. Ask anything.

[ Chat widget loads here — powered by Reese ]
The Alternative

What you're replacing.

A human receptionist costs between $35,000 and $50,000 per year in salary alone — before benefits, PTO, training, and turnover. They cover one shift. They handle one conversation at a time. They can't be on your homepage chat widget and your sales line simultaneously.

A call center handles volume — but not context. Every caller starts from zero. There's no CRM lookup before the call. There's no department handoff after. There's no task created. The call ends; the information disappears.

An Always-On Agent costs $750/month. It works every shift. It handles every channel simultaneously. It knows your knowledge base, your calendar, and your CRM on every call — not just the ones that got routed to a senior agent.

Human receptionist$35–50K/yr + benefits · Business hours only
Call center$25–40K/yr contract · No CRM threading
Call-routing software$300–500/mo · Transfers only — no AI
Always-On Agent (Palatai)from $750/mo · 24/7 · all channels · CRM-connected
Pricing

Hire an Always-On Agent from $750/mo.

Hire Reese — Receptionist Department

$750/mo

+ $2,500 one-time setup

  • Voice
  • Chat
  • SMS
  • Email routing
  • Reese's persona included

The Receptionist department includes Always-On Agents across all four channels. This is the all-in-one hire.

Hire Reese →

Add to Any Department Hire

+$750/mo

+ $2,500 one-time setup per agent

  • Voice
  • Chat
  • SMS for that department's named agent

Already hiring Vance for Sales? Add his own number and chat widget for +$750/mo. Vance answers in Sales persona — not as a generic receptionist.

See all departments →
FAQ

Common questions about Always-On Agents.

Palatai uses a Bring-Your-Own-Provider (BYO) model. You connect your own Retell account for voice and your own Twilio account for SMS. Palatai handles the AI, the persona, and the CRM threading — the carrier relationship stays with you. If you don't have a Retell or Twilio account, the guided setup walks you through connecting one in under 15 minutes. A 14-day trial sandbox lets you test with a shared number before committing to your own.
Yes, with the calendar integration active. The agent can check availability, propose slots, and confirm bookings inline during the call or chat — no hold music, no callback required. Bookings appear on your kanban board as tasks and on your connected calendar. Supported integrations: Google Calendar (live); others via the integrations page.
Yes. You can configure any named agent to operate in a different language or in multilingual mode. Reese, for example, can be configured as a Spanish-speaking receptionist for a specific phone number without affecting other channels. This is done through the employee's persona settings — no separate product tier required.
The agent has access to your knowledge base — the FAQs, business details, and instructions you've configured. If a question falls outside that scope, the agent does one of three things (configurable per employee): offers to take a message and have someone follow up, warm-transfers to a human, or tells the caller honestly that it will escalate. It does not hallucinate answers. The escalation path is set when you onboard.
An IVR is a routing system. It sends callers to extensions based on key-presses. It cannot answer a question, qualify a lead, book an appointment, or create a CRM record. An Always-On Agent is an AI employee — it has a name, a persona, a knowledge base, and the ability to take action. The caller has a conversation. The agent produces outcomes.
Yes. Each phone number and each chat widget can be assigned to a different employee. Your main number routes to Reese. Your sales line routes to Vance. Your /docs page chat routes to Sage. This is set once at configuration; the routing is automatic after that. You can change the assignment at any time from the employee's settings.
Yes — a 14-day trial sandbox. You get a shared phone number from Palatai's pool to test inbound calls and SMS before connecting your own Retell and Twilio accounts. Web chat works immediately with no setup. Trial includes up to 100 voice minutes and 200 SMS. No credit card required for the trial; billing starts when you go live with your own provider connection.
Get Started

Hire your first
Always-On Agent.

Pick up every call. Answer every chat. Reply to every text. Your AI employee starts today — no phone-tree setup, no scripts to write, no shifts to cover.

Hire an Always-On Agent →