KiliChat Help

Appearance

Starter flows ​

Starter flows are ready-made chatbots you can copy and change. They're a quick way to get a working flow in minutes.

How do I use a starter flow? ​

  1. Go to Automation → Flows and click New flow.
  2. Under Start from, click a starter. Its "To do:" note says what you must change.
  3. Change the Flow name if you like.
  4. Click Use this and open builder.
  5. Make the changes from the "To do" note, and adjust the wording to your business.
  6. Test it, then click Save and turn on.

Your copy is yours to edit. Changing it doesn't affect the starter or anyone else.

Which starters are there? ​

Greets customers with three buttons: See products, Order help and Talk to us.

  • Starts when the message is exactly hi, hello or menu.
  • See products sends a link button to your catalogue.
  • Order help asks for the order number, saves it to order_id, thanks them and hands the chat to your team.
  • Talk to us says someone will reply soon and hands the chat to your team.
  • To do: change the catalogue link to your website.

Lead capture ​

Asks an interested customer for their name, city and need, tags them as a lead and hands over to sales.

  • Starts when the message contains price, interested or details.
  • Asks for their name (saved to full_name and copied into the contact's name), city (saved to city) and what they're looking for (buttons, saved to interest).
  • Adds the tag Lead, thanks them and hands over.
  • To do: rename the Product A and Product B buttons.

TIP

Make a sequence that starts on the Lead tag to follow up automatically if sales can't reply straight away.

Order status lookup ​

Asks for an order number, looks it up in your store's system and replies with the status.

  • Starts when the message contains order status, track or where is my order.
  • Asks for the order number (saved to order_id).
  • An API call step fetches https://your-store.example.com/api/orders/{{attr.order_id}} and saves the status from the reply to order_status.
  • If it worked: "Order 1042: Shipped. Anything else? Reply MENU for options."
  • If it failed: says sorry and hands the chat to your team.
  • To do: put your store's order API address in the API call step, and the field that holds the status. Your developer or store provider can tell you these.

Book an appointment ​

Collects the service, preferred day and time, then passes the request to your team.

  • Starts when the message contains book or appointment.
  • A list menu of services (saved to service), a question for the preferred day (saved to preferred_day), and buttons for Morning, Afternoon or Evening (saved to preferred_time).
  • Adds the tag Appointment request, confirms the request and hands over.
  • To do: change the services in the list to yours.

TIP

For proper day and time menus, swap the day question and time buttons for one Pick date & time step.

Feedback ​

Asks how the experience was. Happy customers get a review link; others are asked what went wrong.

  • Starts when the message is exactly feedback.
  • Three buttons: 😊 Great, 😐 Okay, 😞 Not good (saved to rating).
  • Great sends a link button to leave a review.
  • Okay or Not good asks what could be better (saved to feedback), adds the tag Needs follow-up, apologises and hands over.
  • To do: change the review link to your Google review page.

Can I start a starter flow from a broadcast? ​

Yes. For example, send a template with a quick reply button Feedback, and change the Feedback flow's keyword to exactly match the button text. Everyone who taps it starts the flow. See Start a flow.