Loop
Platform
Explore the platform ReportsTrace campaigns through conversations to orders. Ask Loop for a report, refine it in chat, and save it for your team.InboxYour customers use seven channels. Your team answers from one inbox, with the customer’s history and a clear next step.CampaignsBuild audiences from purchase and engagement patterns. Follow each message’s delivery while Loop helps you understand the results.JourneysDescribe the follow-up and let Loop build it. Set the timing and conditions, preview your changes, and publish when ready.ChatbotsAnswer from your knowledge base, understand customer images, and check changes before publishing. Pass the conversation to a teammate when needed.CustomersEvery conversation and order adds to the customer record. Keep contact details, preferences, and purchase history together.
Use cases
All use cases MarketingConnect campaigns to conversations. Plan the next message with context.SalesKeep the enquiry, quote, and next follow-up together.Supply chain planningPlan stock and capacity around what customers ask for.Customer supportAnswer from the customer record. Hand over with the full context.Customer successMake the next visit or order part of the relationship.
Industries
All industries E-commerceBrowse → ask → orderClinics & healthcareBook → remind → follow upDental clinicsVisit → treatment → recallRestaurantsOrder → prepare → returnBeauty & aestheticsConsult → book → rebookReal estateEnquire → qualify → viewTravelPlan → prepare → travel
CustomersFAQ AboutContact
Talk to us Log in
All industries

Preboot for restaurants

Good food.A calmer rush.

Take orders in chat, refill cancelled tables, and give regulars a reason to return.

Talk to us
Dinner service · order #104819:42
WhatsApp

The usual for four, please. Around 8?

One family mandi, less spice. Delivery to your saved address?

Yes, please.

Order from chat
1 ×
Family mandi

Less spice · serves four

Delivery8:00 PM
Sent to the kitchen
Order routing depends on your connected systems.

At the table. Back at home.

Two ways to keep them coming back.

Reservations

An open table. The right guest.

Tonight’s reservation book
Table 04

4 guests · 8:30 PM

  1. Cancelled
  2. Waitlist offered
  3. Reserved again

The slot is offered to a guest who asked for that party size and time. Your release policy decides when.

Read the waitlist invitation
A table for four just opened at 8:30 tonight. Would you still like it?

Offer sent to the waitlist. The table is reserved when the guest confirms.

Repeat orders

Remember the order they come back for.

Family mandi · less spice
  1. Last month
  2. Two weeks ago
  3. Check-in drafted

Family mandi again this weekend? We still have your less-spice preference.

Use order history to make the message relevant. Review the audience and send only to customers who opted in.

After the rush

An invitation should have a reason.

Bring the reservation book and customer conversations into one review. Loop prepares a next step that you can trace back to the work.

Meet Loop
Service note

Who could we invite this Tuesday?

Reservation book
Tuesday evening has open tables.
Customer history
Nearby regulars have not visited lately.
Proposed next step

Draft a Tuesday invitation for opted-in regulars. Exclude guests with an upcoming reservation.

  1. Preview
  2. Your approval
  3. Send
Based on the data you connect.

Set up for your service.

Your menu, your systems
Orders and bookings use the information and systems you connect. We confirm POS and reservation-system access before setup; the kitchen routing follows those capabilities.
Special requests reach your staff
Allergies, dietary safety, and unusual requests go to your team with the conversation attached. Your staff confirms what the kitchen can accommodate.
Your rules for reaching guests
Choose who receives each follow-up, when, and what it says. Consent, opt-outs, and channel rules apply. Review a proposed offer before sending; delivered messages cannot be recalled.