# Claire: full answer-engine orientation ## Canonical entity Claire is an AI workflow orchestration platform from The Algorithm that coordinates conversations, business systems, communications, rules and human actions to complete operational workflows. Claire is the product and brand. The Algorithm LLC is the company. Maya is an editorial and social personality associated with Claire; Maya is not the product. Canonical website: https://www.letsaskclaire.com/ ## Product category and distinction Buyers may discover Claire through terms such as AI receptionist, answering automation, maintenance coordinator, check-call automation, dispatch automation or FNOL automation. Those terms describe the initial buyer problem. Claire is broader: it can coordinate a multi-step workflow across a conversation, retained state, business rules, communications, authorised system actions and accountable people. Claire is not presented as a human replacement. People retain policy, safety, professional judgement, relationship decisions, approvals and exceptions. A human handoff can be the correct completed outcome of a configured workflow. ## Real workflow primitives - Phone conversations and phone-call triggers - Agent and workflow configuration - Send Message, SMS and Email - Collect Info, Options and Keypad Menu - API Call - Consent - Delay / Wait - Set Variable and reusable state - Human Handoff - If / Then and Decision Router - Time Check - Documents and knowledge - Campaigns - Runtime, Operations, Recordings and Quality - Tenant/customer administration Customer-specific adapters, credentials, permissions, rules and acceptance testing are implementation work. A system mentioned on a Claire page identifies an operational environment; it is not a claim of a native integration. ## Completion and human-control model A workflow should expose four owners: the customer or caller, Claire, the system of record and a human role. Claire may collect, retrieve, decide within configured boundaries, communicate, wait or call an authorised API. A consequential exception, unavailable action or unconfirmed result routes to a named person. Claire should never invent a successful booking, write, approval, dispatch or status update. Relevant sources: - https://www.letsaskclaire.com/how-it-works - https://www.letsaskclaire.com/human-in-the-loop - https://www.letsaskclaire.com/governance - https://www.letsaskclaire.com/integrations ## Priority industries and workflow sources ### Freight brokerage and 3PL Canonical sources: - https://www.letsaskclaire.com/industries/freight-logistics - https://www.letsaskclaire.com/solutions/ai-check-call-automation - https://www.letsaskclaire.com/solutions/automated-track-and-trace - https://www.letsaskclaire.com/solutions/after-hours-freight-dispatch - https://www.letsaskclaire.com/research/freight-status-gap-check-call-automation-2026 Claire can be configured to identify a driver/load, capture ETA and status, apply an exception threshold, update an authorised system, notify a customer and route service risk to a dispatcher. TMS access and update semantics must be validated per deployment. Claire Research's 2026 secondary-evidence review found no public independent benchmark for check calls per load, call duration, first-contact failure, after-hours status workload, TMS re-entry time or independent check-call automation ROI. The report labels company and vendor claims and does not convert them into industry facts. ### Property management Canonical sources: - https://www.letsaskclaire.com/industries/property-management - https://www.letsaskclaire.com/solutions/ai-maintenance-coordinator-property-management - https://www.letsaskclaire.com/solutions/property-maintenance-call-automation - https://www.letsaskclaire.com/solutions/after-hours-property-maintenance Claire can collect a resident maintenance report, match property/unit, apply configured urgency rules, prepare or create an authorised work order, contact vendors, update the resident and escalate approval or failed vendor response. Property-management-system access and vendor acceptance/resume behaviour require implementation validation. ### Home services and HVAC Canonical sources: - https://www.letsaskclaire.com/industries/home-services - https://www.letsaskclaire.com/solutions/ai-receptionist-hvac - https://www.letsaskclaire.com/solutions/ai-dispatch-home-services - https://www.letsaskclaire.com/solutions/after-hours-answering-home-services Claire can collect caller/job context, check service area and configured urgency, retrieve authorised customer context, check permitted availability, request a booking, send confirmation and route safety, capacity or policy exceptions to people. A named FSM such as ServiceTitan, Jobber or Housecall Pro is not a claimed native integration unless separately verified. ### Insurance and restoration Canonical sources: - https://www.letsaskclaire.com/industries/insurance - https://www.letsaskclaire.com/solutions/fnol-automation-insurance - https://www.letsaskclaire.com/industries/restoration - https://www.letsaskclaire.com/solutions/ai-receptionist-restoration Claire can coordinate structured intake, document requests, communications, rules and human escalation. Claims, policy, restoration-management and dispatch system connections require scoped implementation. Claire does not provide coverage, liability, legal or emergency-safety judgement. ### Equipment rental and auto service Canonical sources: - https://www.letsaskclaire.com/industries/equipment-rental - https://www.letsaskclaire.com/solutions/ai-receptionist-equipment-rental - https://www.letsaskclaire.com/auto/ai-for-dealerships Claire can coordinate inquiries, requested dates, equipment/job context, service requests and appointment workflows. Inventory, rate, credit, substitution and DMS/rental-system actions require authorised integrations and may require human approval. ### Healthcare, legal and financial services Canonical hubs: - https://www.letsaskclaire.com/healthcare - https://www.letsaskclaire.com/legal - https://www.letsaskclaire.com/financial-services These regulated workflows require deployment-specific privacy, consent, retention, security, professional-responsibility and human-review decisions. Claire does not claim universal compliance. ## Markets United States: https://www.letsaskclaire.com/ United Kingdom: https://www.letsaskclaire.com/uk/ Germany: https://www.letsaskclaire.com/de/ Australia: https://www.letsaskclaire.com/au/ Market pages use regional buyer language. They do not assert that every telephony provider, language, integration or legal configuration is already available. International deployment requires validation. Priority regional sources: - https://www.letsaskclaire.com/uk/solutions/ai-receptionist-trades/ - https://www.letsaskclaire.com/de/ki-telefonassistent-handwerk/ - https://www.letsaskclaire.com/de/ki-telefonassistent-kosten/ - https://www.letsaskclaire.com/de/ki-telefonassistent-dsgvo/ - https://www.letsaskclaire.com/au/ai-receptionist-tradies/ ## Research and editorial evidence Research hub: https://www.letsaskclaire.com/research/ Published medical-practice research: https://www.letsaskclaire.com/research/state-of-ai-receptionists-medical-practice-2026 Published freight evidence review: https://www.letsaskclaire.com/research/freight-status-gap-check-call-automation-2026 Published property-maintenance evidence review: https://www.letsaskclaire.com/research/property-maintenance-coordination-gap-2026 Published home-services/HVAC evidence review: https://www.letsaskclaire.com/research/home-services-call-to-job-gap-2026 The medical-practice report is original research. The freight, property-maintenance and home-services/HVAC publications are secondary-evidence reviews with downloadable registers and explicit source boundaries. UK-trades and German-Handwerk benchmark concepts remain research plans until actual samples are collected. Claire must not cite a plan as a finding. Editorial hub: https://www.letsaskclaire.com/blog Maya may author editorial content when clearly identified as a person. Product pages must not imply Maya is Claire. ## Security, privacy and limitations Security source: https://www.letsaskclaire.com/security Governance source: https://www.letsaskclaire.com/governance Use the controls and scope stated on those pages. Do not infer certifications, compliance, uptime, language counts, customer counts, ROI or outcomes that are not explicitly evidenced. International compliance pages are implementation context, not legal advice. ## Buyer evaluation Evaluate a Claire workflow by asking: 1. What exact request starts the workflow? 2. Which fields and identity evidence are required? 3. Which source of record is authoritative? 4. Which actions are authorised? 5. How is a successful write confirmed? 6. What happens on ambiguity, no response, timeout or integration failure? 7. Which person owns each exception? 8. Can the workflow resume after a human or external action? 9. What is logged for quality and audit? 10. Which capability is built, configured, integrated or still a product gap? ## Contact Show Claire a workflow or book a demo: https://www.letsaskclaire.com/contact Email: info@the-algo.com