Governed social posting, built from your approved knowledge.

Your team can receive a notification when someone submits a contact enquiry. The chat widget captures the customer's email address and message, then sends the team an email notification for follow-up. For example, if a customer says they want someone to get back to them about a service, they can leave their details through the widget. Your team then has the message rather than relying on someone noticing a half-finished chat later. To reduce spam, there is a one-contact-submission-per-session limit. That keeps the route useful without inviting the same person to hammer the form six times in a row.

Webhooks for lead notifications may be supported where it is within scope and the destination endpoints and data fields are agreed and approved. If you need confirmation for a specific client scenario, please contact our team for the agreed terms and a written confirmation.

Your team can receive a notification when someone submits a contact enquiry. The chat widget captures the customer's email address and message, then sends the team an email notification for follow-up. For example, if a customer says they want someone to get back to them about a service, they can leave their details through the widget. Your team then has the message rather than relying on someone noticing a half-finished chat later. To reduce spam, there is a one-contact-submission-per-session limit. That keeps the route useful without inviting the same person to hammer the form six times in a row.

Your team can receive a notification when someone submits a contact enquiry. The chat widget captures the customer's email address and message, then sends the team an email notification for follow-up. For example, if a customer says they want someone to get back to them about a service, they can leave their details through the widget. Your team then has the message rather than relying on someone noticing a half-finished chat later. To reduce spam, there is a one-contact-submission-per-session limit. That keeps the route useful without inviting the same person to hammer the form six times in a row.

The available information does not confirm a separate partner login route. Please get in touch with the team for specific details. If you are a partner, use the access instructions given to you rather than assuming the client route is the same. For example, a partner may need different materials from a client account, so it is better to confirm the right entry point before sharing anything with your staff. That keeps your access clean and avoids mixing partner discussions with client operating tools. Once confirmed, save the correct link clearly.

Repeated contact forms can turn useful follow-up into admin confetti. The contact enquiry route limits each session to one contact submission to reduce spam. For example, if a customer leaves their email address and message through the widget, your team receives an email notification for follow-up. The same session should not keep producing duplicate contact alerts every few seconds. That helps your staff focus on genuine enquiries rather than sorting through repeated copies of the same message. It also gives the customer a clearer path: leave details once, then wait for the team to respond. Not glamorous, perhaps, but tidy beats chaotic most days.

Your team can receive a notification when someone submits a contact enquiry. The chat widget captures the customer's email address and message, then sends the team an email notification for follow-up. For example, if a customer says they want someone to get back to them about a service, they can leave their details through the widget. Your team then has the message rather than relying on someone noticing a half-finished chat later. To reduce spam, there is a one-contact-submission-per-session limit. That keeps the route useful without inviting the same person to hammer the form six times in a row.

Partners can track their support requests through the designated support interface or communication channel associated with their account. Availability depends on the defined partner support structure.