- Data in Lexer's CDP
- Lexer's Attributes
- Attribute Value Types
- Data Source - CRM
- Data Source - Transactions
- Data Source - Email
- Attributes - Personal
- Attributes - Retail
- Attributes - Inferred Gender
- Attributes - Predictive Model
- Attributes - Email
- Attributes - Activate
- Partner Data - Experian
- Partner Data - Mastercard
- Partner Data - Roy Morgan
- GDPR/CCPA Requests
- Upload Data Files
- File Upload API
- Data Provision & Schemas
- Customer Data
- Guide to using Respond
- Inbox Filtering
- Forms for Service
- Workflow States
- Bulk Changes
- Scheduled Replies
- Message Templates
- Finding Conversations
- Customer Profiles
- Grouped Messages
- Automation Rules
- Redact Messages
- Routing Customer Replies
- Chatbot User API
- Troubleshooting Respond
- Interact with Comments/Tweets
- Adobe Campaign
- Amazon S3
- Campaign Monitor
- Cheetah Digital
- Facebook Ads
- Google Display & Video 360
- Google Ads
- InMoment (formerly MaritzCX)
- Instagram Ads
- Offline Conversions [beta]
- Pinterest Ads
- Retention Science (ReSci)
- Salesforce Marketing Cloud
- Snapchat Ads
- Swift Digital
- TikTok Ads
- Twitter Ads
A guide to the workflow states for conversations
As part of your workflow, an object is either “Open” or “Closed”. There are one of twelve States that an object can be in at any moment.
It’s brand new. None of your team have touched it yet.
An agent has been assigned this object, or has taken ownership of it.
An agent is currently writing a response to this object.
A reply has been sent on this object.
The object has been assigned to someone to approve the drafted response.
Acts as a flag on the object to indicate this requires a follow up action.
Indicates the query has been taken offline, and redirected elsewhere within your organisation.
The object has been responded to, and is closed.
This has been automatically closed as one of the older objects in a thread from the same author.
Only the newest message in a thread will be left in an open State for you to action.
The object is irrelevant to the workflow or the business.
The object is a duplicate of another in the workflow.
No Response Required
No response is required on this object.
How are they used?
States are either automatically assigned based on actions that you take, or they are manually changed.
Think of them as states of a ticket, or a request - your action depends on the stage (state) of the ticket (object).
Naturally, the action you take is up to you! States are an indicator that are open to your interpretation and workflow.
Manually change a State
- Select an object from your workflow by clicking on it.
- Under Workflow State and Owner, the first dropdown you’ll see should have now changed to show the State as Assigned. From here, select the appropriate State.
Automatically applied States
Some States are automatically applied to objects, based on an action you perform, or where they sit in your workflow, or a conversation thread.
How it’s applied
All new messages that appear in your Inbox will land with the ‘New’ State applied.
Updated to this State when a ‘New’ object is selected from the Inbox.
Updated to this State once you start typing a reply on an ‘Assigned’ object.
Once an object has been submitted for approval, this State will be displayed.
Applied to an object as soon as a response is published on an object.
Applied to all but the newest message in a conversation thread. Read more about this here.
Searching based on States
To search for objects based on their State, add the search filter Current State to your Deep Dive, selecting the State/s you’re looking for (or select all - except those you’re not - if you’re wanting to exclude them from your search).