Custom Objects
Each customer's contract, tickets and product, where your CSM can see them.
Create the objects of your business, a Contract, a Support ticket or a Dev ticket, and link their records to the customer and their journey. Before a meeting, a renewal or a go-live, your CSM finds these records on the customer's journey.
7-day free trial.
When a dev ticket holds up the go-live, the CSM sees it on the journey.
An admin creates the Dev ticket object with a name, a description and an icon. The ticket opened for this customer links to their journey in the Relations tab, next to the delivered product and the signed contract. Each record has its own Drive, variables and permissions.
The contract is coming to an end. Its end date is on the customer record.
Give the customer a Date variable, Contract end, and an Object reference variable that points to the record of their contract. Both show in the Variables tab of the customer record. Type "@" in the renewal email, and Sekential puts this customer's date there.
Before a meeting, open the customer record. The customer's team and journeys are there.
The Overview shows their ongoing journeys with their weather and their latest meetings. Contacts show as a list or as an org chart, from the manager down to their team. A contact's record keeps their recent meetings and the next steps noted in meetings.
What Custom Objects does
Objects
System objects
Customers, Journeys and Products exist in every workspace and can't be archived.
Custom objects
An admin creates an object: name, description, icon.
Records
Each record has its own Drive, variables and permissions.
Journey relations
A journey links to its customer and to the records that concern it, from any object.
Integration objects
Your Slack channels, Notion databases and HubSpot companies become objects; you choose which records to sync.
Variables
Six variable types
Text, number, yes or no, date, list of options, reference to a record.
Required variables
A variable can be mandatory for each customer or each journey. A customer becomes active once its required variables are filled in.
Insert with @
In the portal, forms and emails.
Native variables
Customer name, Journey name, Portal link, ready from the start.
A step sets a value
A Playbook's flow writes a variable's value when it passes through this step.
Playbook variables
A Playbook declares its own variables.
Customer record
Customer record
Five tabs: Overview, Contacts, Drive, Variables, Permissions.
Contacts org chart
As a list or as an org chart, with a filter by manager.
Contact record
Their recent meetings and the next steps noted in meetings.
Customer Outcomes on the customer record
SoonThe Customer Outcomes of the customer's journeys, read from their record.
Contact profile
SoonTheir role in the decision, their influence, and what the team knows about them, each fact with its source.
Questions about Custom Objects
System objects and custom objects
Who creates an object
Linking a contract to a customer
Data from HubSpot, Slack or Notion
Required variables
Deleting an object
Your contracts and your tickets, where your CSM keeps up with each customer.
7-day free trial.