Lifecycle: Allow changing Lifecycle via automation
complete
Naman Bhatnagar
Business problem:
Updating lifecycle manually limits automation. Additionally, without proper webhooks and triggers for Lifecycle, users cannot build automations around Lifecycles of Contacts
Desired outcome:
- Allow the ability to change Lifecycle via automation, such as workflow step. Triggers and webhooks would also help users create automations when Lifecycle changes for contacts.
- This could help automations with other integrations such as GSheet, HTTP calls, etc.
N
Nabilah Binti Salleh
complete
We’re excited to announce that our Lifecycle feature has its own Trigger, Step, and Webhooks! ⚡
Now, you can streamline sales workflows, automate actions based on Lifecycle Stage changes, and keep CRM data seamlessly synchronized. Learn more here: https://respond.canny.io/changelog/automate-sales-processes-with-our-lifecycle-trigger-step-and-webhooks
Naman Bhatnagar
Nabilah Binti Salleh Amazing! thanks Rio team!
D
Davi Peyroton
Is there a maximum deadline for this feature to be released?
Y
Yihui Chan
Hi Davi Peyroton, we're working hard to release this soon but it should be available before the end of this year.
Y
Yihui Chan
in progress
Y
Yihui Chan
Merged in a post:
Lifecycle Webhooks
D
Davi Peyroton
Problem: We have logs of when a lifecycle is changed directly on the conversation window but we'd like to send data to somewhere else with the chat data.
Example: A webhook is sent when a conversation is closed and all the conversation data is sent within it. We want to send the chat/contact data through a webhook when a lifecycle stage is changed.
Use case:
- Update our CRM status according to the lifecycle stage on respond.io
- Get contact/conversation data to generate enhanced reports outside respond.io
Y
Yihui Chan
planned
Mat Ward
Should also be able to update contact fields based on lifecycle. If lifecycle is changed from lead to customer, we should be able to trigger a workflow to update certain contact fields
Isaac Cespedes
This is the first thing I tried to do when starting with the lifecycle feature. I see a lot of potential usage, but in the workflows are missing. It is a must-have for automating stages.
E
Encuesta NPS
Isaac Cespedes You're absolutely right. Life cycles must be triggers or conditioners in workflows.
C
Chris Elder
I just started experimenting with Lifecycle and also found this limiting issue.
Interestingly you can automate the lifecycle updates via Zapier but not within Respond itself.
Without automation, Lifecycle stages will always be out of date or not updated by all staff and therefore, in time, no one will rely on its accuracy within our team.