Two NativeCall service records: restaurant cancellation and hotel confirmation

These two examples show what a completed phone enquiry can establish. In both, the first attempt did not resolve the task and a real person followed up. They are first-party service records, checked against our task history and customer replies in September 2026.

We have omitted names, venues, contact details, booking references, travel dates and direct customer quotations. The private records are retained for internal verification. We do not publish them or turn customer acknowledgements into testimonials.

What the records confirm

For more documented bookings, cancellations, accommodation and delivery outcomes, browse our customer story collection.

For your own request, ask for the recipient’s answer to each question separately. “We reached the hotel” does not mean it agreed to hold your room; “the reservation is cancelled” does not mean a refund was issued.

Restaurant: cancelling an existing reservation

Request: Contact a restaurant to cancel an existing booking, rather than make a replacement reservation.

What happened: The first attempt did not resolve the task. A real person followed up, made further attempts to reach the restaurant, and reported that the restaurant had located and cancelled the booking. The customer acknowledged the result after receiving that update.

Recorded outcome: The service history contains an explicit cancellation result and a subsequent customer acknowledgement.

What to prepare for a similar call: The correct venue and branch, booking name, date, time, party size and reservation reference. Ask separately whether the booking is cancelled, whether a charge remains due, and whether written confirmation is available.

Compare restaurant booking and calling options, make a translated call yourself, or submit a restaurant task.

Hotel: confirming that a reservation exists

Request: Check an existing hotel booking and ask about a confirmation email.

What happened: The first attempt did not resolve the request, and a real person followed up. The operator recorded that the hotel located the reservation under the guest name. The hotel directed the confirmation-email request back to the booking website. The customer subsequently asked whether the booking was confirmed, received an explicit confirmation from the operator, and acknowledged it.

Recorded outcome: The task history documents a booking confirmation communicated to the customer. It also records a separate next step: requesting written confirmation from the booking website.

What to prepare for a similar call: The property name, guest name as entered when booking, stay dates, booking platform and reservation reference. Ask who is responsible for sending the confirmation and which channel to use if the hotel cannot provide it directly.

Read the hotel arrival guide, make a translated hotel call, or submit a hotel enquiry.

Choose the right route for your request

With a translated self-call, you participate in the conversation through the app. The recipient answers a normal phone call. Repeat important details and ask what has actually been confirmed.

With a delegated task, a real person calls in Japanese and finishes your task within 24 hours. Read the current scope, price and timing on the linked service page before paying. The recipient’s availability and policies still determine what can be done.

A connected call or a completed payment alone is not proof that a request has been accepted.