Bosque Software Inc.Bosque Software Inc.

Bosque Blog

A calmer chat, and a clearer way to reach a person

November 6, 2026

This walkthrough shows a recent update to a client chat. The people using it are often upset, in a hurry, or both. The changes make the conversation easier to follow, and they make it easier to reach a person.

This 3-minute, 47-second walkthrough has no audio. A complete text description follows below.

What a visitor gets:

  • The greeting stays on screen. New replies start at the top and come in at a steady pace, so you can read them in order.
  • You can scroll while a reply is still arriving. The start of the reply stays put until you move.
  • A message from a staff member appears all at once, so a person is easy to tell from the assistant. A long staff reply still opens at the beginning.
  • Before a staff member joins, the chat asks for a name, the pet's name, a ZIP code or a city and state, and a way to reach you. Staff start with what they need.
  • If you would rather keep talking here, you can. What you already typed is still there if you reload the page.
  • If the connection fails, those details are saved. You can try again without filling the form a second time.
  • If no one is available, the chat says so before it tries to connect you.
  • A price question that also comes from grief gets both things in the reply. The cost is there, and so is an acknowledgment of what the family is going through.
  • Questions about grief support and aftercare get a direct answer. When a price has to be confirmed, the chat says that.
  • Urgent danger goes straight to the right help. A pet who cannot breathe is directed to an emergency veterinarian. A person in immediate danger is told to call 911. Suicidal thoughts, without an immediate physical emergency, are pointed to 988.

Walkthrough text description

The recording shows a demonstration chat beside a panel explaining each scenario. The panel and chat change together. A greeting identifies the assistant as digital, lists common reasons for contacting the care team, and asks for the visitor's name, pet's name, and reason for reaching out. An availability notice appears above the conversation. A notice below it explains that chat is not an emergency service. The following describes the full sequence; the names and contact details entered are demonstration data.

  1. Confirm details before connecting. The visitor sends “Please connect me to a human.” A “Connect to Client Care” form asks for the visitor's name, pet's name, ZIP code, and email or phone. A link switches from ZIP code to city and state. The demonstration fills the fields, confirms them with “Connect me,” and shows the connection to the care team. The alternative “Keep chatting instead” remains available before submission.
  2. Keep chatting or reconnect. The visitor opens the contact form and then chooses to continue chatting. The conversation returns without losing the draft. Reopening the form or reloading the page in the same browser session preserves the unsent details.
  3. Retry a failed connection. A connection attempt fails. The chat reports the failure and allows another attempt. The visitor's confirmed details remain filled in rather than requiring entry again.
  4. Availability changes. The care team becomes unavailable while the visitor is preparing to connect. The chat explains the change before attempting a connection, so the visitor is not left expecting someone to join immediately.
  5. Grief and pricing together. The visitor says their dog has lymphoma, describes feeling devastated, and asks the price of a home visit. The response acknowledges the distress and addresses the pricing question in the same reply.
  6. Misuse is redirected. A request to reveal the assistant's hidden instructions receives a short refusal. The assistant offers help with the care team, services, grief resources, or connecting with Client Care instead. This request does not create a handoff.
  7. Emergency help is never gated. The visitor reports that their dog cannot breathe and is collapsing. An emergency notice immediately directs them to veterinary care. Completing a contact form is not required to see that direction.
  8. Emergency help cannot wait. An urgent personal medical-danger message interrupts the normal connection process. The notice tells the visitor to call emergency services rather than wait for chat. It cancels the intake flow and persists after reconnection. A return-to-non-emergency-chat control is also demonstrated.
  9. Crisis support through 988. The visitor describes suicidal thoughts following the death of their dog. The displayed U.S. crisis-support notice provides “Call 988” and “Text 988” actions, distinguishes immediate danger with a “Call 911” action, and explains that chat cannot dispatch help. Outside the U.S., the notice directs the visitor to local emergency or crisis services.
  10. Aftercare and grief support. A visitor asks about grief support and aftercare costs after their cat's death. The response acknowledges the loss, offers grief-support resources, and explains that the care team can confirm the specific aftercare options and pricing.
  11. Read from the beginning. The visitor requests a long, eight-paragraph overview. The assistant's reply appears progressively from its beginning. The assistant icon and opening text stay in view instead of jumping to the bottom as more text arrives. The visitor can choose to scroll while it is still arriving.
  12. A human reply does not stream. The visitor connects to Client Care. The staff reply appears as a complete message, distinguishing it from the progressively displayed assistant response. A long staff message also opens at its beginning.

The recording ends after the human-response demonstration. It contains no speech, music, or other sound.

Need production-grade AI engineering?

Bosque helps founders and CTOs move from prototype to production with strategy and implementation under one roof.