Question 1

What is Atlas?

Accepted Answer

Atlas is a Mac app from Teleperson that handles the companies you deal with: it calls them for you, waits on hold, remembers what they said, and checks your bank to make sure they do what they promised. See how it works on Atlas.

Question 2

Who is Atlas for?

Accepted Answer

Anyone who deals with companies — which is everyone. Atlas is most useful if you have a lot of companies to keep track of (banks, insurance, subscriptions, utilities, internet and phone) and would rather not spend an hour on hold to get a simple thing done.

Question 3

How do I get Atlas?

Accepted Answer

Atlas is in beta. We're inviting people in small groups — join the Atlas beta and we'll email you when your invite is ready.

Question 4

Is there a Windows or phone version?

Accepted Answer

Not yet. Atlas is for Mac today.

Question 5

How much does Atlas cost?

Accepted Answer

Consumer is free. Plus is $19 a month or $190 a year, and Pro is $99 a month or $990 a year (annual plans include two months free). Enterprise is custom. Plus and Pro each come with a 14-day free trial; when a trial ends without a subscription, the account drops to Consumer. Calling is an invite-only pilot while live audio is reviewed. See what's in each plan on Atlas pricing.

Question 6

What's included in each plan?

Accepted Answer

Consumer includes Today (briefing, Needs-you inbox, money check-in), Vendor Hub, the cancel assistant, disputes and promise tracking, 3 Atlas requests a month and one bank connection, using your own AI keys. Plus adds 50 phone minutes and 100 hosted AI requests a month, unlimited Atlas requests, talking to Atlas by voice with the “Hey Atlas” wake phrase, and unlimited bank, mail and calendar connections. Pro adds 200 phone minutes and 500 hosted AI requests a month, a chief of staff (morning brief, week-ahead review), representative calls, and receipts and expense reports. Enterprise adds custom limits, invoicing, a security review and a named contact. See the full comparison on Atlas pricing.

Question 7

Does Atlas pretend to be me?

Accepted Answer

No. Atlas always tells the company it's an AI assistant calling for you. It never enters payment details, and you can take over any call.

Question 8

Where is my data kept?

Accepted Answer

Call history, transcripts, notes and your home address stay on your Mac. Bank connections run through Plaid, so Atlas never sees your bank password. Full detail on Security.

Question 9

How does Atlas make a call?

Accepted Answer

Pick a company and tell Atlas why — say, "refund the double charge." Atlas brings the charges, your past calls and the right phone menu, dials the verified number, says up front that it's an AI, works through the menu, and waits on hold. You can listen live and take over any time.

Question 10

What happens while I'm on hold?

Accepted Answer

Atlas waits for you. YouZak plays your podcast while you're queued and brings you back the moment a person answers.

Question 11

How does Atlas make sure companies follow through?

Accepted Answer

Refunds, cancellations and lower prices promised on a call are tracked against your bank. If a promise isn't kept, Atlas tells you, and a follow-up is waiting.

Question 12

What is a dispute pack?

Accepted Answer

When you're double charged or a price jumps, Atlas puts together the charges, what the company said and when, and ready-to-send drafts for the company and your bank.

Question 13

Why does this exist?

Accepted Answer

Customer service is broken on both sides — costs more every year, satisfies less every year. We think the path through is agent-to-agent commerce: a consumer agent that knows you, talking directly to brand agents that know their company, with a neutral marketplace layer between them. The full thesis is on Our Next Chapter, and the field map is in The Architecture of Agent-to-Agent Commerce.

Question 14

Is Atlas just another AI chatbot?

Accepted Answer

No. ChatGPT, Siri and Muse answer questions; Atlas deals with the companies for you. It's an advocate that works for you across every company, not for any one brand trying to deflect you.

Question 15

Who's building this?

Accepted Answer

Co-founders Jesse Hollander (CEO) and Eben Hall (COO), with a team of operators and engineers from across consumer software, fintech, and enterprise CX. Meet everyone on the team page.

Question 16

What does Teleperson sell to companies?

Accepted Answer

Three things, in order of integration depth: The AI agent — a branded chat-and-voice agent on your site that recognizes each customer and resolves routine requests on the first turn. The B2B platform — the dashboard, CRM, growth, and insights behind the agent, connected to your existing support stack and routing complex cases to your humans. Agent-to-agent integration — for design partners, a direct connection between your brand agent and the consumer agents that represent your customers. Full positioning on For Business.

Question 17

How is this different from Intercom Fin, Sierra, Decagon?

Accepted Answer

Those products give the brand a better chatbot. We give the brand a better surface to meet the consumer's agent on — because the next architecture of customer service has agents on both sides of the conversation. The long-form argument is in The Connective Tissue Argument and From One-to-One to One-to-Many.

Question 18

Do you replace our existing helpdesk or chatbot?

Accepted Answer

No — we sit alongside it. Most deployments keep the existing helpdesk (Zendesk, Salesforce, Intercom) and add Teleperson as a new surface that talks to the same backend. We're additive, not rip-and-replace.

Question 19

What kind of results have you seen?

Accepted Answer

First production deployment is the specialty pharmacy case study — read the numbers there. We're early; we publish wins when they're real, and we'll talk you through the maths in a demo call.

Question 20

What is the Design Partner program?

Accepted Answer

A small cohort of brands working with Teleperson directly to ship the first production agent-to-agent integrations. Design partners get senior engineering attention, custom integration work, and a seat at the table on the protocol decisions that will shape the category. Program details and the application form are on Our Next Chapter.

Question 21

How long does it take to go live?

Accepted Answer

Six to eight weeks from first call to live integration for the design-partner cohort. The first two weeks are scoping (what does success look like, which support flows, which systems to integrate), then four to six weeks of build and pilot.

Question 22

What does Teleperson need from us to start?

Accepted Answer

Three things: an executive sponsor, a technical owner who can grant integration access to the systems we'll connect (helpdesk, knowledge base, identity), and a defined success metric. The first scoping call is free and non-committal — book one.

Question 23

Is the Design Partner cohort still open?

Accepted Answer

Yes, on a rolling basis with a hard cap on cohort size so each partner gets full engineering attention. Apply through Our Next Chapter and we'll be back to you within 48 hours.

Question 24

How much does it cost?

Accepted Answer

Custom, scoped per deployment. Pricing depends on volume (interactions, deflections, agent-to-agent transactions), integration depth, and SLA. We don't publish list pricing because every deployment is sized to the brand's actual support footprint. Book a demo and we'll scope a number on the first call.

Question 25

What's the contract structure?

Accepted Answer

Annual contracts with a usage-based component. Most deployments are a base platform fee plus a per-resolved-interaction fee — aligned to outcomes, not seats. We wrote about why per-seat pricing doesn't work for agentic platforms in Pricing Agentic Outcomes.

Question 26

Is there a free trial?

Accepted Answer

Not in the conventional sense — but the design-partner program functions as one. The first two-week scoping period is free and gives both sides a chance to validate fit before commercial terms.

Question 27

What security standards do you meet?

Accepted Answer

Encryption in transit and at rest, row-level isolation between tenants, audit logging on all data access, and SSO/SAML for admin surfaces. SOC 2 Type II is in process; HIPAA-eligible deployment patterns are available for healthcare design partners. Full detail and the security questionnaire pack live on Security.

Question 28

Where does data reside?

Accepted Answer

US-region cloud (AWS) by default. EU-region deployment is available for design partners with EU customer data; we can support data-residency and data-processing addenda as part of the standard contract.

Question 29

Do you sign a DPA?

Accepted Answer

Yes. Our standard DPA is on /legal/dpa; we also accept partner-supplied DPAs for review. Sub-processor list is published and updated within 30 days of any change.

Question 30

Are you HIPAA-compliant?

Accepted Answer

Yes for design partners — we'll execute a BAA and deploy in a HIPAA-eligible configuration. Our first production case study is in specialty pharmacy, so the controls are exercised in a real regulated workflow.

Question 31

How do you handle PII?

Accepted Answer

Segregated per tenant, encrypted at rest with per-tenant keys, and never used for foundation-model training. Logs and observability data are pseudonymised in pipeline. Full detail is in the security questionnaire pack — request it through your design-partner contact.

Question 32

What verticals does Teleperson serve?

Accepted Answer

Strongest current footprint is in specialty pharmacy and healthcare (read the case study), with active design-partner conversations across financial services (banks, credit unions, insurance), telecom, and consumer subscription brands. The platform is vertical-agnostic; the depth comes from the design-partner work that follows.

Question 33

What systems do you integrate with?

Accepted Answer

Helpdesks (Zendesk, Salesforce Service Cloud, Intercom), knowledge bases (Notion, Confluence, Guru, your own), identity (SAML/OIDC, Auth0, Okta), and conversation surfaces (your existing chatbot, your voice IVR). Custom integrations are part of the design-partner scope.

Question 34

Do you support voice?

Accepted Answer

Yes — voice runs in the same agent as chat, on real-time WebRTC infrastructure (Vapi), with brand-customised voice ID, prompt, and routing. Multi-language support shipping across English, Spanish, French, German, Portuguese, Italian, and Japanese.

Question 35

Who founded Teleperson?

Accepted Answer

Co-founders Jesse Hollander (CEO, three-time founder, formerly Frost & Sullivan and Mizuho) and Eben Hall (COO, three-time founder, 25+ years across enterprise IT and startup execution). Meet the rest of the team on the team page.

Question 36

Where are you based?

Accepted Answer

Distributed across the US — leadership in Madison, WI and Duluth, GA, with engineering and design across multiple US time zones. We meet in person quarterly.

Question 37

How are you funded?

Accepted Answer

Funded by a small group of operator angels and a lead institutional investor; we'll publish the round when the time is right. The team is sized for the design-partner cohort, and we're hiring against the next wave of integrations — see Careers.

Question 38

How do I get in touch with the team?

Accepted Answer

For commercial conversations, book a 30-minute call — that's the fastest path. For everything else, Contact routes to the right person (sales, support, security, press).

Everything people ask, in one place.

Question we didn't answer?