Marketplaces, integrations and outbound calls.

1. 1 Public pages: "Guests order pickup/delivery and book tables without calling. Same menu, prices, hours and rules as Ruby." Each page has an on/off switch and a link to copy.
2. 2 Google Business Profile: your location, the two tagged links (tagged, so orders from Google are counted as coming from Google) and Push links to Google.
3. 3 Social bios: "Copy into your Instagram and Facebook bios, or send on WhatsApp."
4. 4 Delivery platforms: Bolt Food and Glovo (module 2).

1. Open SettingsOnline ordering (https://resto.custocareai.com/settings/online). Admin
2. Switch on Online ordering page ("Pickup and delivery with MoMo/card payment links or cash") and Online booking page ("Live table availability; deposits follow your booking rules"). Copy each link.
3. Google Business Profile: type the Location name (as it appears on Google, e.g. Mama's Kitchen Osu) and the Location id (from Business Profile Manager, the number in locations/…). Optionally paste your Review link.
4. Put the links on Google: copy Order online link (for Google) and Reserve link (for Google) into Google (Business Profile → Edit profile → Food ordering / Bookings), or click Push links to Google. "Links sent to Google" confirms.
5. Social: copy the Instagram, Facebook and WhatsApp texts from Social bios.

1. 1 The set-up drawer has three tabs: Setup, Item mapping and Intake log.
2. 2 Receive orders turns intake on; Accept automatically skips the "submitted" step so the kitchen sees the order straight away.
3. 3 Status sync: Sandbox (nothing sent) records what would be sent (see Intake log); Live calls the platform and needs the Platform API token the platform gave you.
4. 4 The Webhook URL and Signing secret you paste into the platform. The secret is shown once ("Signing secret (shown once, copy it now)"); Rotate secret makes a new one.
5. 5 Send test order: a signed sample order through the same intake, tagged TEST. Status sync for it is always sandboxed.

1. Open the platform: SettingsIntegrationsDelivery providersGlovoConnect (or SettingsOnline orderingDelivery platformsSet up). Admin
2. Setup: Store id ("Enter the store id the platform gave you"), Branch ("Where these orders are cooked. Default: your first branch."), Receive orders on, Accept automatically if you want → Create integration.
3. Copy the connection details into the platform's partner settings: the Webhook URL and the Signing secret (copy it now; it is not shown again).
4. Item mapping: Add item → Platform item id, Name on platform, Menu item → Save mapping. Unmapped lines still arrive with the platform's name and are listed as unmapped in the order notes.
5. Test: back on Setup, Send test order and check it appears on the Orders board.
6. Status sync: leave Sandbox (nothing sent) until the platform confirms the connection; then choose Live and paste the Platform API token in its box → Save. A saved token is never shown again ("A token is saved. Paste a new one to replace it.").
7. Watch the Intake log: each order's in and out events, with "Synced: …" when a status reached the platform.

1. 1 Sandbox mode: events are logged, marked Sandbox, and not sent. Turn it off when you are ready: "Sandbox mode off — integrations are live".
2. 2 The cards, grouped as POS & kitchen display, Delivery providers, Booking systems and CRM. A connected card also shows Sandbox or Live.
3. 3 Webhooks: each with Send test, Deliveries (the delivery log) and, for admins, Signing secret.
4. 4 Service keys: only the start of each key is shown, with its permissions and when it was last used.

Connect Square KDS, TableCheck or HubSpot

1. Open SettingsIntegrations → the card → Connect. Admin
2. Enter the credentials the provider gave you in the boxes on the card: Square KDS Access token and Location ID; TableCheck API key and Shop ID; HubSpot Private app token. They are "Stored encrypted and never shown again. Leave empty to run in sandbox mode."
3. Connect. Then open the card again (Configure) and click Send test; Recent deliveries shows the result.

Add a webhook and read its delivery log

1. Add webhook → Endpoint URL (a full https:// address) → tick the Events (order, booking and payment events) → Add webhook. Admin
2. Signing secret → Show secret, and give it privately to whoever runs the receiving system. Every event is signed, so their system can trust it came from your restaurant. Create new secret stops the old one at once ("New signing secret created. Update your endpoint.").
3. Send test: "Delivered", "Logged in sandbox mode (not sent)" or "It was not accepted. See the delivery log." SupervisorAdmin
4. Deliveries: each delivery shows Delivered, Retrying, Failed after 5 attempts or Sandbox · not sent. Failed deliveries are retried automatically for a few hours. Redeliver sends one again now. Rows are kept 30 days.

Service keys

1. Create key → "Create service key": Name ("Which system uses it, e.g. Loyverse POS") and Permissions: AI tools, Conversations or Full access ("Every machine endpoint. Use only for trusted systems."). Admin
2. Copy your new key: "This is the only time the full key is shown. Store it somewhere safe." → I have saved it.
3. Revoke a key you no longer use → Revoke key. "Systems using this key stop working straight away. This cannot be undone."

1. 1 Outbound calls must be on for "Ruby calls them" and for every automation.
2. 2 Booking reminder calls: "Reminder calls before bookings (falls back to SMS if the guest doesn't answer)", with Hours before the booking (1 to 72).
3. 3 Delay calls: "Call about delays on high-value orders when the SMS can't be sent", with Minimum order total.
4. 4 Console softphone: the phone built into the console. It may be switched off by Kasada AI or your partner.

Switch on calls and automations

1. Outbound calls: SettingsFeaturesOutbound calls → on. Admin
2. Automations: same page, card Outbound call automations → switch on what you want → Save automations. AdminSupervisor
3. Order ready and on its way: SettingsNotifications → When an order is ready and When a delivery is on its way → choose Send SMS, Ruby calls the guest, Ruby calls, then SMS if no answer, Call and SMS or Off; set Call from / Call until and Try again once if there is no answer → Save.
4. Review rescue calls: AnalyticsReputation boosterSettings → Review rescue → How: Ruby calls them (see Analytics). If the guest does not answer, the apology message goes instead.

A call by hand, and marketing consent

1. Call a guest from an order, booking, ticket or customer → How: Connect me ("Your phone will ring first; pick up and we connect you.") or Ruby calls them ("Ruby introduces herself and the restaurant, then handles the call."). AdminSupervisorHost
2. Purpose: Call back, Booking reminder, Confirmation, Delay notice, Order ready, On its way, Marketing (needs consent), Other. Add a Note for Ruby → Ask Ruby to call.
3. Marketing calls need the tick The guest agreed to promotional calls (on the Kasada Dialpad: The guest agreed to marketing calls.) and the guest's promotions opt-in. Without both, the call is refused.

The softphone: auto-answer and your sign-in

• The Kasada Dialpad says: "Connect me, Listen in, Join call and Take over ring this dialpad and are answered automatically." Other incoming calls ring normally with Answer and Decline.
• The softphone signs in to the phone system as your own extension, only while you are signed in to the console with a tab open. If you have several tabs open, the last one you opened holds the phone.
• When you sign out, an admin signs you out, or the console signs you out after 5 minutes of inactivity, the softphone disconnects too. Because you can be signed in in only one place at a time, your extension rings in one place only.
• Set your extension in My profile (or ask your admin); without one, "Set your phone extension in My profile to make calls."