Adding chat to an app creates an expectation that someone is listening. For a small business, that expectation needs as much design attention as the message bubbles. Decide what conversations belong in the app, who responds and how the customer knows whether a message was sent, received or answered. A useful conversation should remain connected to the service it concerns.
Attach the conversation to the right context
A customer asking a cabinetmaker about an installation should be able to identify the relevant job and attach an appropriate photograph. Keep the job reference visible so a reply is not mistaken for another project. Distinguish an operational question from an emergency or time-critical request, and show the appropriate contact route when the app is not monitored for that purpose. If several staff members may respond, make the business identity consistent while retaining an internal record of responsibility. Avoid asking customers to repeat information the conversation already contains.
Use status words carefully
Sent, delivered and read imply different things. Only display a status the system can support, and explain a pending message when connectivity is unavailable. A notification may alert someone to a reply, but the conversation should be retrievable inside the app if notifications are disabled. Apple's notification design guidance provides a reference for appropriate alert behaviour. Keep sensitive message details out of lock-screen previews where the product context calls for discretion. Let customers manage optional message alerts without making the conversation history difficult to find.
Plan the human side of response
Set a realistic response expectation and display business hours where relevant. A message submitted late on a Friday should not imply immediate attention if the team returns on Monday. Give staff a way to identify unanswered conversations and hand them over without losing context. Test attachments that fail to upload, two replies arriving close together and a customer returning through an old alert. During the pilot, review whether messaging resolves questions or merely moves an existing phone queue into another inbox. Adjust the scope and staffing before presenting chat as a universal support promise.
- What kinds of questions can the business reliably handle through this channel?
- Does each conversation remain associated with the correct customer task or job?
- Can customers distinguish a pending message from one the business has received?
- Who owns unanswered messages during leave, weekends and changes of shift?