01
Property facts first
Recommendations and drafts begin with approved property information, not invented operational assumptions.
Trust and scope control
Clear boundaries make a modern service credible.
SignalDeskHQ is explicit about what is ready, what requires owner approval and what should only be activated after the right controls exist.
Operating principles
Control is part of the product.
The service should remain useful even before deeper integrations are enabled.
02
Owner approval by design
Pricing exceptions, refunds, sensitive guest requests and material changes remain visible before action.
03
Human-reviewed communication
Guest-facing content is reviewed before external sending unless a separate approved rule exists.
04
Staged automation
Automation expands only after permissions, fallback paths, monitoring and responsibility are explicit.
Scope map
Know what happens now, after approval and later.
- Property assessment
- Listing and proof review
- Guest-support drafts
- Owner approval workflow
- Weekly operating brief
- Pricing exceptions
- Date or policy changes
- Refund questions
- Sensitive guest complaints
- External account changes
- WhatsApp provider sends
- Payment collection
- Calendar write-back
- OTA adapters
- Autonomous external actions
Governed workflow
Source, draft, approve, audit.
A simple control loop keeps the service understandable as capabilities expand.
Source
Use approved property facts and explicit owner rules.
Draft
Prepare a recommendation or response with visible assumptions.
Approve
Route material decisions to the accountable owner or operator.
Audit
Retain the decision, action and outcome for review.
Start with evidence