Skip to main content
GullySystem
Automotive

WhatsApp, SMS and Email Notifications for Airport taxi services

Send business messages from approved events and recipient rules.

Platform

Does this function belong in your operation?

Use when people need consistent updates triggered by business records.

An order, payment, booking or task reaches a notification event.

Trace a shared system record used for “Airport pickup with flight tracking”. Include who creates it, which branch or team uses it, and how corrections are controlled.

Bring the records the workflow depends on.

  • Message events
  • Recipient permissions
  • Approved channel accounts and wording

Outputs to check

  • Message event and recipient log
  • Delivery and failure status
  • Retry or follow-up queue

Follow the whatsapp, sms and email notifications workflow.

Use this sequence to compare your current process with the proposed module. Agree the owner, permission and exception at each step.

  1. 1. Define the trigger

    Specify the business event and the message it justifies.

  2. 2. Select recipients

    Apply contact, permission and audience rules.

  3. 3. Prepare the message

    Use the approved content and required event details.

  4. 4. Submit through the channel

    Retain the attempt reference and distinguish queued from delivered status.

  5. 5. Resolve failures

    Correct invalid details or retry under the agreed duplicate-control rule.

Who uses the module, and who approves?

Keep responsibilities distinct even when one person holds more than one role.

Office assistant

Reviews event messages, checks recipient details and resolves failed or withheld submissions.

Accounts assistant

Checks financial message content and follows up delivery failures without changing the underlying ledger.

Owner

Reads what went out in the business’s name. Every word is on file.

Decide how exceptions are handled.

These business rules belong in configuration and testing. A normal transaction alone does not demonstrate that the workflow is ready.

Invalid recipient

Hold the message and request a corrected address or number.

Provider rejects message

Record the reason and retry only under the agreed rule.

Event repeated

Use the event reference to avoid unintended duplicate messages.

Can this work independently?

Notifications depend on a source event and an authorised delivery channel. They can use file or manual triggers, but order, booking or payment systems provide more reliable references. Provider acceptance, delivery and human reading are distinct outcomes and should not be treated as equivalent.

Systems and records it connects with

  • Collections and follow-up: Due balances, payment promises and follow-up outcomes.
  • Invoice management: Issued invoice references, line amounts and outstanding balances.
  • Appointment scheduling: Confirmed slots, cancellations and attendance outcomes.
  • Service reminders: Due-service triggers and follow-up outcomes.

Configure, test and introduce the workflow.

  • Gather the messages your staff type today. We write back which can come from records and which stay manual.
  • You approve wording and languages. Templates arrive for each channel, ready for the approval step WhatsApp requires. Sender details come from you. Share the WhatsApp number, SMS account and email, and a test message reaches your own phone before customers see any.
  • Go live small. A handful of customers receive live messages, staff check delivery status, and the office is trained.

Check the result before rollout.

Apply these checks to a sample from the agreed workflow, then repeat with an exception. Keep the expected result beside the test record.

  • A repeated event does not send unintended duplicates.
  • Recipient rules respect recorded permissions.
  • Failures are visible for follow-up.
Airport taxi services

How the business operates.

An airport taxi operator takes advance bookings, counter requests or travel-desk orders and allocates suitable cars and drivers to pickup times. The passenger, the person booking and the paying organisation can be different people. Flight changes, terminal instructions and waiting charges affect dispatch and billing. This illustrative operating model fits an operator managing bookings and trips; a marketplace matching independent drivers requires a different commercial and technical scope.

Booking desk and account service

Record passenger and booker contacts separately, alongside flight, terminal, destination, vehicle class and fare agreement. A hotel or corporate account needs its billing reference and the person authorised to change a booking.

Dispatch and holding-lot coordination

Allocate a driver and car against pickup time and availability. Where the operator runs a holding-lot queue, keep entry and release decisions visible. A revised arrival time needs acknowledgement rather than an assumed change.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Booking number, booker, passenger and payer contacts
  • Flight, terminal, pickup point, destination and vehicle class
  • Fare rule, waiting allowance and approved extra charges
  • Driver allocation, vehicle assignment and acknowledgement

Operational bottlenecks to check

The flight changes but dispatch does not

A new arrival time is useful only if the dispatcher and assigned driver receive and acknowledge it. Define how the desk responds when a feed or message is unavailable.

Booker and passenger receive different information

A family member or travel desk can hold the booking while the traveller's phone is offline. Specify which details reach each contact and who is authorised to request a change.

How work flows across this business

This module sits within a wider operating process. Use the sequence to identify the other teams and records affected by a change.

  1. 1. Capture and confirm the booking

    Record who is travelling, who booked and who pays. Confirm the pickup instructions and fare basis before treating the car request as accepted.

  2. 2. Review arrival changes

    Update the expected arrival through the agreed manual process or supported feed. Record who acknowledged the changed pickup time and whether the original car and driver remain available.

  3. 3. Allocate the car and driver

    Check availability and the operator's readiness criteria before dispatch. A reassignment needs a recorded reason and updated information for the people relying on the earlier confirmation.

  4. 4. Perform and record the trip

    Capture pickup, destination and completion against the same trip number. Waiting, tolls and other extras need the agreed evidence and approval treatment rather than an unlabelled amount added at settlement.

  5. 5. Reconcile the shift

    Compare trip records with coupons, collected fares and approved expenses. Keep an unexplained difference visible with an owner instead of changing the fare retrospectively to make the cash total fit.

  6. 6. Bill accounts and resolve exceptions

    Prepare corporate or hotel statements from the agreed trip records. Follow disputed charges, cancellation adjustments and missing trip evidence before marking the account period complete.

Industry reports to connect with

  • Bookings and completed trips by pickup period, destination and vehicle class
  • Unassigned, reassigned, cancelled and missed-pickup bookings
  • Driver and vehicle availability against committed trips
  • Shift settlement differences and unapproved extra charges

Questions before implementation.

When should airport taxi services consider whatsapp, sms and email notifications?

Use when people need consistent updates triggered by business records. An order, payment, booking or task reaches a notification event.

What should we bring to the requirements discussion?

Bring anonymised examples of Message events; Recipient permissions; Approved channel accounts and wording. Show who creates, checks and changes each record. Use only records from an activity that meets the suitability conditions above.

Does this replace our existing business software?

The starting point is your current system and the gap you need to close. Send business messages from approved events and recipient rules. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

Messaging depends on provider availability, account permissions and current channel rules.

How are scope, price and rollout decided?

The proposal follows a review of your records, user roles, branches and existing software. Data migration, connections, training and support are scoped separately where needed. A repeated event does not send unintended duplicates. Use this check when reviewing the first working version.

Talk to us

Discuss whatsapp, sms and email notifications for your business.

Tell us which workflow needs attention and which systems your team uses. The next step is a requirements discussion and a written scope.

What happens after you share your requirements

  1. We review your brief and the systems you already use.
  2. We clarify the workflow, missing information and the work to consider first.
  3. The proposed scope sets out the deliverables, responsibilities and dependencies.
  4. Review the scope and commercial terms before deciding whether to proceed.

Start with your requirements

Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

Share your requirements