SUPPORT CHAT
“Please provide your transaction reference” is where support goodwill goes to die. In FinLabCore’s client apps, a support request starts from the record: the client attaches the exact payment, transaction, currency exchange, counterparty, wallet or file the issue concerns, and the conversation begins with context, not with an interrogation.
Six object types can anchor a request, each with its own picker: the client selects the actual payment, transaction, exchange, counterparty, wallet, or file from their own data, one or several, and the request carries it. Support investigates the thing itself instead of reconstructing it from a description, which is precisely what cuts the clarification round-trips.
Every request starts structured: a category, a subject that becomes the conversation’s title, and the message that opens it, validated before sending, so no half-formed tickets enter the queue. Classification routes the request to the right support flow from message one, not after a triage exchange.
Everything about an issue stays in its conversation: follow-up messages, additional attachments, replies pinned to specific messages, copyable text, downloadable files, and a list view showing every chat’s subject, latest activity and current status. Reachable from the sidebar or header, inside the same product where the records live, no channel-switching, no “as I said in my email.”
Attach the record, send, and watch it arrive in the back office with the context already open.