Customer support and ticket tracking for hospitality and accommodation businesses | DASNET
Ticket workflows give an issue an owner, priority, status, timeline and resolution record so follow-up does not depend on a single person's inbox.
This guide explains the workflow, how to prepare, which checks matter and how to handle common exceptions for hospitality and accommodation businesses.
Explore DASNETDeveloper documentation
Understand the workflow, apply the checklist, and confirm which payment channels and features are enabled for your account before using them in production.
What Customer support and ticket tracking means for hospitality and accommodation businesses
Ticket workflows give an issue an owner, priority, status, timeline and resolution record so follow-up does not depend on a single person's inbox. For hospitality and accommodation businesses, the goal is to coordinate bookings, deposits, final bills and refunds. A reliable workflow makes the request, responsible person, reference and final outcome visible rather than leaving the process in disconnected messages.
The operational challenge
A common challenge is that booking changes and cancellations can create differences between expected and actual payment amounts. When the source request, payment status and business record do not line up, staff can repeat work or act on an assumption. A consistent process separates initiation from completion and records the evidence used to make a decision.
A practical end-to-end workflow
- Capture the problem, impact, relevant time and non-sensitive reference.
- Assign an owner and priority based on impact and urgency.
- Keep status updates and customer communication connected to the ticket.
- Document the resolution and avoid including passwords, OTPs or API secrets.
A workflow shaped around this use case
- Tie each payment to a booking reference and applicable terms.
- Track deposits, balances, cancellations and refunds separately.
- Confirm the final transaction before closing the booking account.
How DASNET fits
DASNET is a business workspace for supported payment workflows and everyday business operations. Depending on account configuration, teams may use it to manage payment requests and collections, review transaction records, handle supported wallet and payout activity, organise invoices or bills, and keep customer and operational information together. The precise menu, channel and automation available to a business should be confirmed in its account. DASNET is not a promise that every payment rail, bank destination or provider feature is automatically enabled.
Controls and measures to review
- Track the number of unresolved items and how long they remain open.
- Separate pending, successful, failed, reversed and disputed outcomes in reports.
- Keep a clear owner for exceptions and a reference for every consequential action.
- Review access permissions and avoid storing credentials or sensitive authentication data in notes.
- Compare material payment totals with trusted provider or bank records.
Frequently asked questions
What should a ticket include?
Include the issue, expected versus actual result, timestamp and non-sensitive transaction reference.
Should a ticket contain an OTP or password?
Never. Authentication secrets must remain private.
How do teams avoid lost tickets?
Use explicit ownership, status transitions, escalation and regular review of ageing issues.
When can a ticket be closed?
When the resolution is verified, the outcome is documented and any required customer follow-up is complete.
How does this apply to hospitality and accommodation businesses?
The main objective is to coordinate bookings, deposits, final bills and refunds. Start with the workflow and controls on this page, then verify the exact features enabled for your DASNET account.
What should we do if a payment or record looks wrong?
Pause any consequential action, keep the non-sensitive reference and timestamp, check the trusted source record, and follow your documented support or reconciliation process. Never share PINs, OTPs, passwords or API secrets.
Does DASNET guarantee that every feature is enabled?
No. Product availability depends on account setup, permissions, provider approvals and enabled services. Confirm the live configuration before making operational commitments.
Related DASNET guides
Continue with these related workflows:
M-Pesa STK Push for hospitality and accommodation businesses · STK Push integration guide for hospitality and accommodation businesses · Safaricom Daraja API workflows for hospitality and accommodation businesses · Online payment links for hospitality and accommodation businesses · Customer payment requests for hospitality and accommodation businesses · Merchant payment collections for hospitality and accommodation businesses