Question 1

What is Typelessity?

Accepted Answer

Typelessity is an AI conversational booking widget that replaces traditional multi-step booking forms with a single natural-language chat. It supports 25+ languages, voice input via Whisper, and real-time enrichment APIs. It is configured per industry — current production verticals include clinics, legal practices, hospitality, beauty, real estate, automotive, and education.

Question 2

How does Typelessity differ from Calendly?

Accepted Answer

Calendly is a scheduling-link tool — it shares a calendar and lets people pick a slot. Typelessity replaces an entire booking form with a conversation that can collect any structured data: specialty, doctor, dates, slots, addresses, vehicle types, dietary requirements, and dozens of other fields. Use Calendly for simple meeting links, Typelessity when the booking has more than two or three fields.

Question 3

How does Typelessity differ from SimplyBook.me?

Accepted Answer

SimplyBook.me is a full booking platform with built-in payments, staff scheduling, inventory, and customer accounts. Typelessity replaces only the booking form with conversation, then submits to your existing backend via webhook or REST POST. Use SimplyBook when you need an end-to-end booking system with payments. Use Typelessity when you already have a backend (CRM, calendar, payment processor) and want to replace the front-end form with a 25-language chat.

Question 4

How does Typelessity differ from Cal.ai?

Accepted Answer

Cal.ai is an outbound AI phone-calling feature built into Cal.com Workflows — it places lifelike voice calls to confirm bookings, send reminders, and follow up on no-shows, billed per minute. Typelessity works the other direction: it is an inbound conversational widget on your own site that collects a complete, structured booking through chat in 25+ languages and submits it to your backend. They sit at different layers and pair well — Cal.ai can chase a no-show after Typelessity captured the booking. Use Cal.ai when your gap is outbound reminder and confirmation calls on top of Cal.com; use Typelessity when your gap is the inbound intake form itself.

Question 5

How does Typelessity differ from Botpress?

Accepted Answer

Botpress is a chatbot framework — you build conversation flows yourself with a visual editor, and you maintain that bot. Typelessity is a turnkey booking widget configured by us in a few hours from your spec, with a single GPT call extracting every field at once and anti-hallucination guards baked in. Use Botpress when you need a custom-built bot for a non-booking use case. Use Typelessity when you specifically want to replace a booking form and want a working integration the same day, not after weeks of engineering.

Question 6

How does Typelessity differ from NoForm.ai?

Accepted Answer

NoForm.ai is a top-of-funnel lead-qualification tool — it captures interest and routes leads to sales. Typelessity completes a structured booking with all required fields (specialty, date, time, name, contact, dietary preferences, etc.) and submits it to your booking system. Use NoForm for marketing lead capture. Use Typelessity when the user is ready to book, not just inquire.

Question 7

Does Typelessity work in non-English languages?

Accepted Answer

Yes. Typelessity supports 25+ languages out of the box including English, Russian, German, French, Spanish, Italian, Polish, Portuguese, Dutch, Turkish, Arabic, Hebrew, Japanese, Korean, and Chinese. The configuration language sets the response language; user input can be in any supported language and will be translated and normalized automatically.

Question 8

How accurate is the data extraction?

Accepted Answer

Typelessity uses gpt-4.1-nano with a unified prompt that reads each field's aiHint. Extraction accuracy on typical service-industry configs is >95% for first-attempt structured fields. The system never uses hardcoded regex patterns — GPT reads the config and extracts based on semantic context. Anti-hallucination guards ensure GPT only commits values the user explicitly mentioned.

Question 9

What does 'enrichment' mean?

Accepted Answer

Enrichment is a real-time API call that triggers when a specific field is filled. For example: when a user says "cardiologist", Typelessity calls GET /doctors?specialty=cardiology, receives a list of doctors, and presents them as interactive cards. Up to 5 enrichments per config. 10 second timeout each. Failures are non-fatal — the AI falls back to asking the user directly.

Question 10

How long does integration take?

Accepted Answer

Typically a few hours with personal onboarding. Step 1: fill the client spec template (your fields, options, enrichments, branding). Step 2: we generate a config JSON. Step 3: drop one HTML script tag onto your page. Step 4: hook up your booking API endpoint via the webhook field-mapping you provided.

Question 11

Is Typelessity GDPR compliant?

Accepted Answer

Yes. The widget includes a configurable consent flow shown before any AI processing begins. Data is processed in EU regions when configured. Session data is retained per your retention policy. Right-to-erasure supported via session deletion API. No data is used for model training.

Question 12

Does Typelessity support voice input?

Accepted Answer

Yes. Voice input is powered by OpenAI Whisper. Users tap the microphone, speak naturally, and the transcription is fed into the same extraction pipeline as typed text. Voice works in all 25+ supported languages.

Question 13

How does Typelessity handle corrections?

Accepted Answer

If a user changes a previously filled field, the system detects the correction (GPT signals it via a "correction" key), then walks the dependency graph and clears any downstream fields that depended on the changed value. Destructive cascades show a confirmation: "Changing X will also clear Y, Z. Proceed?"

Question 14

What is the per-turn latency?

Accepted Answer

Median per-turn latency is 200–800ms on gpt-4.1-nano, with a single AI call per turn. When enrichment triggers (a second AI call to present API results), latency adds 1–3 seconds. We do not use gpt-5 in the hot path because of its higher latency.

Question 15

Can I self-host Typelessity?

Accepted Answer

On-premise deployment is available on the Enterprise plan. The widget runs as a Lit web component, the API is a Next.js service, and the AI provider can be swapped between OpenAI, Azure OpenAI, or any OpenAI-compatible endpoint.

Question 16

Does Typelessity replace my booking system?

Accepted Answer

No. Typelessity replaces the booking form, not the booking backend. It collects structured data via conversation and submits it to your existing system via webhook or REST POST. Your CRM, calendar, payment processor, and staff scheduler stay exactly as they are.

Question 17

How much does Typelessity cost?

Accepted Answer

Free Pilot ($0): up to 50 submissions/month — full feature access, personal onboarding. Starter ($39/mo, coming soon): up to 500 submissions/month. Pro ($149/mo, coming soon): up to 2,000 submissions/month, priority support. Enterprise ($399/mo, coming soon): up to 6,000 submissions/month, dedicated success manager.

Question 18

Will conversational booking convert better than my current form?

Accepted Answer

Head-to-head A/B testing is the only honest answer. We provide A/B testing tooling during the pilot so you measure lift on your own traffic against your existing form. We do not publish a hero conversion-lift number on this site because every claim of that shape we have seen in the AI-booking space is either uncited or based on a study with assumptions that do not transfer.

Question 19

What industries is Typelessity best for?

Accepted Answer

Any service business that takes appointments. Production verticals include beauty salons, legal practices, real estate, automotive services, hospitality, education, fitness, pet services, home services, travel, and more. The same engine handles every vertical — configuration changes the field schema, prompts, and enrichments per tenant.

Question 20

Does Typelessity work for AI agents (not humans)?

Accepted Answer

Yes — by design. The same widget API is callable by autonomous agents. We publish a stable JSON schema for sessions today, and the dedicated /agent endpoint (synchronous turn-by-turn API with the same field-extraction pipeline) is shipping Q3 2026. Documentation and schemas are already on /for-ai-agents so agents can be designed against the contract now.

Question 21

Is data encrypted in transit and at rest?

Accepted Answer

Yes. All client traffic uses TLS 1.3. Session data at rest is encrypted with AES-256 in our managed EU-region database. Field-level encryption is available on Enterprise for high-sensitivity flows.

Question 22

Where is conversation data physically stored?

Accepted Answer

Default deployment uses EU regions (Frankfurt, Paris). Enterprise can pin to a specific region, including on-premise / self-hosted where data never leaves the customer's infrastructure.

Question 23

How long is conversation data retained?

Accepted Answer

Default retention is 90 days for completed sessions and 24 hours for abandoned sessions. Both are configurable per tenant down to "no persistence beyond the booking submission" if your backend stores the final record itself.

Question 24

Is OpenAI training on my customer conversations?

Accepted Answer

No. We send every request with the OpenAI data-opt-out flag enabled, which means the conversation is not used for model training. This is the contractual default for our pilots and is documented in the DPA.

Question 25

What is the breach notification process?

Accepted Answer

GDPR-mandated 72-hour notification to affected customers via the contact on file. Post-mortem disclosure (root cause, scope, remediation) within 14 days. Security disclosures: security@typelessity.com (PGP key on request).

Question 26

Do you provide a DPA (Data Processing Agreement)?

Accepted Answer

Yes. A standard GDPR-compliant DPA is included with the pilot package. We also accept customer-provided DPAs with a 5–10 business-day review turnaround.

Question 27

Which sub-processors does Typelessity use?

Accepted Answer

Current sub-processor list is published at /legal/sub-processors. Core ones: OpenAI (extraction), Vercel and AWS Frankfurt (hosting), Resend (transactional email), PostHog EU (analytics — only with explicit consent). Changes are notified 30 days in advance.

Question 28

How do I handle right-to-erasure (GDPR Article 17) requests?

Accepted Answer

Two paths: (a) DELETE /api/session/{sessionId} via the admin API, which removes the session record and propagates to backups within 24 hours; (b) a request to dpo@typelessity.com if the end user cannot identify the session directly.

Question 29

Can I exclude users by region from analytics?

Accepted Answer

Yes. The consent banner is region-aware (GDPR for EU, CCPA framing for California, plain "essential only" elsewhere). Functional and analytics cookies are off by default and only fire after explicit user consent.

Question 30

Is Typelessity certified for US healthcare (HIPAA)?

Accepted Answer

No, and we don't target US healthcare. The widget is configurable for non-US health-adjacent flows (wellness, fitness, EU clinics under GDPR) but US healthcare with HIPAA/BAA requirements is an explicit non-goal until we ship the relevant attestation.

Question 31

What does the embed snippet look like in production?

Accepted Answer

One <script> tag with a tenant-specific bundle URL and a data-config attribute. The public CDN at cdn.typelessity.com/widget.js is shipping Q3 2026; until then, pilot customers receive a tenant bundle URL during onboarding (configured for your domain, with CSP-safe loading).

Question 32

How does the widget submit to my backend?

Accepted Answer

Two options: (a) Webhook — the widget POSTs the structured Booking JSON to your endpoint with optional HMAC signature; (b) REST POST — you provide the endpoint shape and field mapping in your config and the widget calls it directly from the browser with a short-lived token.

Question 33

What is the JSON shape of a submitted booking?

Accepted Answer

Stable schema: `{ bookingId, sessionId, fields: {...}, submittedAt, status }`. Full schemas (Session, Booking, /agent request/response) are published on /for-ai-agents and version-pinned with a `schemaVersion` field.

Question 34

Can I customize the AI prompt itself?

Accepted Answer

You customize via `aiHint` per field — a short instruction telling GPT what each field means semantically. The system prompt is single, unified, and not editable per tenant; that's the architectural guarantee that gives us anti-hallucination behavior and predictable latency.

Question 35

How does cascade-aware correction work?

Accepted Answer

Field dependencies are declared in config (e.g. `doctor depends_on specialty`). When the user changes an upstream field, the system walks the dependency graph via DFS and clears downstream-stale values. Destructive cascades surface a confirmation: "Changing specialty will clear doctor and time slot — proceed?"

Question 36

What happens if an enrichment API call fails?

Accepted Answer

Non-fatal. Each enrichment has a 10-second timeout. On failure, the widget falls back to asking the user directly (e.g. "I couldn't fetch doctor list — please type the doctor name"). Errors are logged with full context for your debugging.

Question 37

Is there an /agent endpoint for autonomous AI agents?

Accepted Answer

Shipping Q3 2026. The contract is finalised and published on /for-ai-agents — agents can be designed against it today. The endpoint is a synchronous turn-by-turn API with the same field-extraction pipeline as the human-facing widget, just without the chat UI.

Question 38

How do I test the integration before going live?

Accepted Answer

Every pilot includes a dev tenant with a test booking endpoint. You receive synthetic-data conversations to validate field mapping, webhook delivery, error handling, and rollback behavior before pointing the widget at your production submit URL.

Question 39

We use Calendly today — how do we migrate?

Accepted Answer

You keep Calendly for the slot pick if it works for you; Typelessity replaces the intake form that captures specialty, requirements, contact info, and dietary/insurance details before the slot. Hybrid integration: Typelessity submits the intake JSON to your CRM or directly into Calendly's webhook.

Question 40

We use SimplyBook.me — what changes?

Accepted Answer

SimplyBook stays as your booking backend (calendar, staff, payments). Typelessity replaces only the front-end form. The migration is one config: map Typelessity field outputs to SimplyBook's booking API. Typical setup time: 1 day.

Question 41

We have a custom HTML form — how do we replace it?

Accepted Answer

Field mapping in your tenant config maps Typelessity extraction output to your existing API's expected JSON shape. We never ask you to rewrite the backend. If your form is multi-step with conditional fields, the cascade dependency feature replaces the conditional logic on the front-end side.

Question 42

We tried Botpress and it was hard — what is different about Typelessity?

Accepted Answer

Botpress is a chatbot framework: you build the flow yourself, you maintain it. Typelessity is turnkey — config in a few hours for a booking-specific flow with anti-hallucination guards already wired up. Use Botpress when you need a custom general-purpose bot; use Typelessity when the use case is bookings specifically.

Question 43

We use NoForm.ai for lead capture — does Typelessity replace it?

Accepted Answer

Different layer. NoForm is top-of-funnel marketing lead capture; Typelessity is structured booking with all required fields completed before submit. Many customers use both: NoForm on the marketing site, Typelessity on the booking page.

Question 44

How does Typelessity compare to Acuity Scheduling?

Accepted Answer

Acuity is in the same class as Calendly — strong for slot picking, weak for multi-field intake. Typelessity replaces the intake; Acuity can stay as the slot backend. If your bookings are simple (1 service, 1 duration, just pick a time), Acuity alone is fine — use Typelessity when bookings have 5+ fields.

Question 45

We use Setmore — when should we switch?

Accepted Answer

When your bookings have grown past simple slot-picking. Setmore handles the calendar well; Typelessity adds natural-language intake on top. Migration is the same as SimplyBook: keep Setmore as backend, replace the intake form. Typical setup: 1 day.

Question 46

We already have a chatbot — can it coexist?

Accepted Answer

Yes. Typelessity is booking-specific and routable. A general chatbot can hand off to Typelessity when intent classification detects a booking ("I want to schedule X"). The handoff is a single redirect with optional context pre-fill via URL params.

Capability	Typelessity	Calendly	Cal.com	Cal.ai	SimplyBook.me	Botpress	NoForm.ai
Interaction model	Inbound chat widget	Slot-pick page	Slot-pick page	Outbound voice call	Booking pages	Custom bot flows	Lead chat
AI natural-language booking	Yes	No	No	Voice, outbound only	Limited	Custom build	Lead-qual only
Multi-language (25+)	Yes	EN-first	EN-first	Per voice config	Yes	Custom build	Limited
Voice input	Yes (Whisper, inbound)	No	No	Yes (phone calls)	No	Custom build	No
Real-time enrichment APIs	Yes	No	No	No	No	Yes	No
Calendar integration	Webhook + API	Native	Native	Native (Cal.com)	Native	Custom build	No
Staff & resource management	Via webhook	Yes	Yes	Via Cal.com	Yes	No	No
Setup time	Hours	Hours	Hours	Hours (in Cal.com)	Days	Weeks	Hours
GDPR-native consent flow	Yes	Yes	Yes	N/A (voice)	Yes	Custom build	Yes
Best for	Replacing intake forms with chat	Scheduling links	Open-source scheduling	Reminder & no-show calls	Full booking ops	Custom chatbots	Lead capture

Bookings through conversation,not forms

TL;DR — What is Typelessity?

How Typelessity works

Chat

Select

Review

Confirm

How the AI actually works

Single unified prompt

Config-driven, not pattern-driven

Real-time enrichment APIs

Cascade-aware corrections

Anti-hallucination guardrails

Reliable by design

Configured for 37 verticals

Typelessity vs alternatives

Simple, Transparent Pricing

Top questions

Get notified when Typelessity launches