I have created many “list hygiene” automations so far, where after an arbitrary time period with no response from a contact, their details are captured in an external database and the contact is deleted in manychat. I do this for a number of reasons, but mainly to keep the active manychat contact list down and manageable.
When a new manychat contact is created, my database is first checked to make sure there is no existing data for this person, but if so, the fields are all populated with the data we have previously archived.
It works great but there needs to be a variable for who the contact was previously assigned to. I have a number of clients who have multiple appointment setters or live chat agents in their manychat accounts. When these contacts re-engage with my clients’ profiles and the fields are all auto-filled from pre-saved data, I need the contact to also get re-assigned back to the original live agent (based on being able to save that data ahead of time).
Yes, I can instruct each of these live agents to assign themself as a tag or as a custom field - manually - each time, but that just seems ridiculous considering how much powerful functionality we already have available to us.
Is this request feasible?
I would love to see it as a data point that can be used in internal conditional queries inside automations, but also to be accessible in the external json payloads in order to parse the date into my external databases or even for use in external automations that are not already integrated in the default setup.
New
API for Chat Assignment
Welcome to the Manychat Community!
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
