- Guest conversations
- Human takeover
- Campaign delivery
- Message status
- Meta Business Verification required
- Template approval may be required
- Meta messaging charges may apply
Leora integrations
Connect Leora to the systems your business already uses.
Leora is designed to work alongside your existing hospitality technology, helping information move between guest conversations, business knowledge and operational workflows.
Integration availability depends on provider access, configuration and plan.
Connection catalogue
Clear capability. Honest availability.
Each connection is labelled by its present availability. Provider-dependent and planned work is not presented as generally available.
Communication
Bring customer communication into a controlled, provider-aware workflow.
- Enquiry notifications
- Operational updates
- Follow-up workflows
- Provider setup required
Guest Experience
Create useful guest touchpoints while keeping handoff and destination boundaries visible.
Website Widget
Live foundation- Embedded guest assistant
- Business knowledge responses
- Structured recommendations
- Human handoff
QR Experiences
Beta- Menu access
- Venue information
- Guest journeys
- Session-based interaction
Google Reviews
Beta- Review-request journeys
- Customer-led submission
- No automatic review posting
- Destination configuration required
Business Systems
Connect context around the systems that continue to own bookings, transactions and customer records.
Booking Systems
Planned / connector dependent- Booking handoff
- Availability checks
- Reservation context
- Provider-specific integration
EPOS
Planned- Product and menu imports
- Sales context
- Redemption tracking
- Provider compatibility required
CRM
Planned- Customer data sync
- Segmentation
- Lead handoff
- Consent and ownership controls
Knowledge Sources
Give Leora access to controlled, business-approved information rather than unsupported assumptions.
Documents
Live foundation- DOCX
- TXT
- Private storage
- Controlled extraction
Menus
Live foundation- Structured menu data
- Prices
- Dietary information
- Allergen records
- Staff verification boundaries
Policies and FAQs
Live foundation- Opening hours
- Services
- Venue policies
- Approved business answers
Developer and enterprise
Support scoped platform connections where access, contracts and security requirements are explicit.
API
Enterprise / planned- Controlled platform access
- Custom workflows
- Tenant-scoped permissions
- Contract and security review required
Webhooks
Beta foundation- Provider events
- Delivery updates
- Signature validation
- Replay protection
Custom integrations
Enterprise- Scoping required
- Provider access required
- Implementation fees may apply
- No unsupported universal connector promise
Integration flow
Context moves. Responsibility stays clear.
- 01
Business systems
Provider-owned records and events
- 02
Leora knowledge and context
Relevant, permitted information
- 03
Guest or staff interaction
A question, request or workflow
- 04
Human review where required
Boundaries and approval remain visible
- 05
Approved action
A permitted next step
- 06
Recorded outcome
An auditable result where supported
How Leora fits
Leora complements existing systems rather than replacing them.
Booking systems
Remain responsible for reservations.
EPOS
Remains responsible for transactions.
CRM systems
Remain responsible for configured customer records.
Meta
Remains responsible for WhatsApp infrastructure.
Leora
Connects context, intelligence and workflows around those systems.
Availability legend
What each status means.
- Live foundation
- Built and available within the current platform foundation, subject to production configuration.
- Beta
- Available for controlled testing and launch-stage use.
- Planned
- Not yet generally available.
- External approval dependent
- Requires third-party approval, access or account configuration.
Trust and control
Connections stay within clear boundaries.
Availability never removes the need for tenant controls, customer consent, provider rules or appropriate human review.
Explore Data and Trust- Tenant-specific access
- Consent-aware customer use
- Human approval
- Provider dependency
- Auditability
- No automatic cross-business data sharing
FAQ
Questions about connecting your systems.
Can Leora replace my booking system?
No. Booking systems remain responsible for reservations. Where a supported connector exists, Leora can use permitted booking context or provide a handoff around that system.
Can I use Leora without WhatsApp?
Yes. Leora’s knowledge, website and operational capabilities do not require WhatsApp. Messaging availability depends on your chosen plan and provider configuration.
Which EPOS systems are supported?
EPOS connections are planned and provider dependent. We will assess the specific system, available interfaces and required permissions before describing support.
Can you build a custom integration?
Potentially. Custom work requires discovery, provider access, technical scoping and security review. We do not promise a universal connector for unsupported systems.
Are provider charges included?
Third-party charges are separate unless an agreed proposal explicitly states otherwise. For example, Meta messaging charges may apply to WhatsApp use.
How long does an integration take?
Timing depends on provider access, approval, data quality, technical scope and testing requirements. A delivery plan is only confirmed after discovery.