01
Messaging / WhatsApp BSP
Designed when enabled
Messaging / WhatsApp BSP
DoubleTick
DoubleTick is listed as designed when enabled — status chips stay honest.
03
Book a demo
External connector
Designed when enabled
Messaging / WhatsApp BSP
Concierge · CRM
doubletick.io
03 phases
Overview
How DoubleTick fits NISKA
Evaluate when WhatsApp or BSP enablement should sit on Concierge and CRM confirm gates.
03Pillars
Three operator outcomes — not a logo wall.
Overview
DoubleTick is listed on the NISKA integrations catalog with status “designed”. DoubleTick WhatsApp Business API provider surface — designed when a BSP is selected for property WhatsApp enablement.
- Guest outreach stays on Concierge and CRM when WhatsApp is enabled
- Confirm gates keep agents from silent writes to guest threads
- Profiles and consent stay DPDP-aligned on the shared CRM model
Why this connector matters
Three operator outcomes — not a logo wall.
Confirm-gated outreach
Concierge and CRM messages stay under Auto / Confirm / Approve — never an ungated blast channel.
One inbox truth
Guest replies land in the same Concierge / CRM workflow staff already operate.
Stay context
Stay and profile context come from the NISKA property model — not a bolt-on inbox silo.
Data paths
What is designed to sync
Flows stay on the shared property model — not a bolted relay layer.
03Paths
Outbound
Confirm-gated Concierge and CRM messages when the messaging surface is enabled.
Inbound
Guest replies land in the same Concierge / CRM workflow staff already operate.
Context
Stay and profile context come from the NISKA property model — not a bolt-on inbox silo.
Surfaces
What this connector covers
Capability language stays tied to Channel Manager / owning modules — not invented APIs.
03Surfaces
- DoubleTick surface in the messaging category
- Enablement is property- and certification-dependent — status chips stay honest
- Actions stay on the NISKA property model with confirm gates where agents write
Enablement
What “when enabled” means
A marketing logo is not a green UAT checklist. Rollout certifies what your property gets.
03Steps
Start here
Select
WhatsApp Business / BSP selection is confirmed for the property.
Step 02
Approve
Templates and consent flows are approved before production sends.
Step 03
Prove
Staff takeover and confirm gates are tested end-to-end.
Day-2 ops
How teams should run it
After go-live, keep the property model as the writer and treat alerts as book-risk.
Keep template ownership with brand / ops owners
Review consent and opt-out handling with compliance
Next step
Map DoubleTick to your property
Book a demo to verify enablement, or return to the catalog for the full grouped list.
Field notes
Sign up to our mailing list for regular updates on the travel & hospitality industry.
Operator-ready briefs on Agentic AI HMS, revenue, Concierge, and India compliance — not vendor fluff.
- Agents & ops
- Revenue
- Compliance