Update lifecycle stage
Keep one current lead stage for each contact, based on evidence.
Use a test channel or sample conversation first. Confirm the visible result in ValueChat before applying the setup to production traffic.
How it works
- 01
When to use
When to use. The conversation confirms a meaningful change in the customer’s buying or service journey.
- 02
Set up permissions
Set up permissions. Add the skill and choose the stages this agent can apply. Use @ to insert a linked allowed stage.
- 03
Example instruction
Example instruction. Move to @Interested only when the customer explicitly requests price or enrollment details. Do not mark a sale as won based on interest alone.
- 04
Customer context
Customer context. Insert $ variables for selected contact fields if a stage decision needs saved information.
- 05
What happens
What happens. The action updates the existing contact lifecycle stage, visible in the customer panel and Contacts. It does not create a separate opportunity.
- 06
Limitations
Limitations. Stage names do not override configured qualification rules. Use the Qualification skill for deterministic required-field checks. An unavailable stage reference must be corrected before saving.
What to verify
✓The expected channel, conversation, contact or execution is visible.
✓The assigned person or agent matches the routing rule.
✓No customer-facing message claims an action that failed.
✓Activity or execution history contains enough context to investigate.
Collect the workspace, channel, conversation and execution identifiers, then contact support@valuechat.app. Never send API keys or passwords.