We run a B2B webshop where every logged-in customer has their own assortment and prices. When a customer logs in, our site calls Tawk_API.setAttributes with their customer number, and it shows up fine in the visitor panel for human agents.
Our AI Assist agent uses an OpenAPI integration to look up products. We’d like the agent to pass the logged-in customer’s identifier to that API, so it can answer with the customer’s own assortment, prices and stock. Right now the agent never sees visitor attributes. It only knows what’s typed in the chat, and asking customers to type their number isn’t an option because anyone could type someone else’s.
What would solve it for us, in order of preference:
Let OpenAPI tool parameters (or a custom header) be bound to a visitor attribute, e.g. a value taken from setAttributes or from Secure Mode / Tawk_API.login, filled in by tawk and not by the model.
Or send a verified visitor or chat ID with every tool call, so our API can look up who is chatting.
Or at least expose visitor attributes to the agent as context.
Option 1 or 2 matters most, since the value has to come from tawk and not from what the model reads in the chat.
In April 2025 it was mentioned here that visitor and client-side metadata would become a context layer for AI agents:
Is there any news or a timeline on that?
Another developer asked about the same thing in the Developers category:
Thanks for sharing your idea and explaining your use case. I’ll pass this along to our team to discuss the possibilities of supporting this functionality or exploring alternative ways to accommodate your requirements.
While I can’t guarantee a timeline for implementation, we’ll keep you updated on this thread or through our community forum if this feature becomes available.