Overview

TitanX automatically writes the work reps do in the app back to Salesforce, so the CRM stays current without any manual data entry. When a rep makes a call, edits a contact, or schedules a follow-up, TitanX creates or updates the matching Salesforce records on its own, using the field mappings set up for the account.

Writes happen as soon as a rep takes an action or a trigger fires. For example, a completed call logs an activity with the outcome and notes, an edited contact field updates the corresponding field on the Contact or Lead, and a follow-up created in TitanX appears as a task in Salesforce.

Task: call activity

Field label	API name	Type	Kind	Notes
Subject	Subject	Text	Standard	Call subject line
Call Result	CallDisposition	Text	Standard	The TitanX disposition name the rep selected
Comments	Description	Long Text Area	Standard	Call notes taken by the rep
Call Duration	CallDurationInSeconds	Number	Standard	Seconds
Status	Status	Picklist	Standard	Set to a completed status
Completed Date/Time	CompletedDateTime	Datetime	Standard	Time the call was logged. TBC
Due Date	ActivityDate	Date	Standard	TBC
Name	WhoId	Lookup	Standard	The Contact or Lead called
Related To	WhatId	Lookup	Standard	The Contact's Account
TitanX User	TitanX_User__c	Text	Package	Name of the rep who made the call
Activity Source Phone	TitanX_Activity_Source_Phone__c	Phone	Package	Caller ID the call was placed from
Activity Target Phone	TitanX_Activity_Target_Phone__c	Phone	Package	Number dialed
Activity Phone Type	TitanX_Activity_Phone_Type__c	Text	Package	Type of the number dialed, for example Mobile or Direct
TitanX Campaign Name	TitanX_Campaign_Name__c	Text	Package	Empty if the call was not part of a campaign
TitanX Campaign Step Name	TitanX_Campaign_Step_Name__c	Text	Package	Empty if not part of a campaign
TitanX Campaign Step Type	TitanX_Campaign_Step_Type__c	Text	Package	For example Call. Empty if not part of a campaign

Task: follow-up

Field label	API name	Type	Kind	Notes
Subject	Subject	Text	Standard	Follow-up subject. TBC
Due Date	ActivityDate	Date	Standard	Follow-up date the rep picks. TBC
Status	Status	Picklist	Standard	Open. TBC
Name	WhoId	Lookup	Standard	Same Contact or Lead as the call. TBC
Related To	WhatId	Lookup	Standard	The Contact's Account. TBC
Comments	Description	Long Text Area	Standard	Follow-up notes, if any. TBC

Contact and Lead

Field label	API name	Type	Kind	Direction	Trigger	Notes
Any edited detail field	Mapped field	Varies	Standard or Mapped	Both	Save in Contact Details, or Log & Finish	Only fields shown in TitanX. Phones, signals and intent can't be edited by reps
Phone 1–5	Mapped field	Phone	Standard or Mapped	SFDC → TitanX	Sync	Up to 5 phone fields chosen in setup
Phone 1–5 Signal	Mapped field	Text	Mapped	TitanX → SFDC	Scoring job	One signal field per mapped phone. Values P1, P2, P3
TitanX Best Phone	TitanX_Best_Phone__c	Phone	Package	TitanX → SFDC	Scoring job	Highest-scoring number. Updates when scores change
TitanX Best Phone Signal	TitanX_Best_Phone_Signal__c	Text	Package	TitanX → SFDC	Scoring job	Signal of the best phone
TitanX Intent	TitanX_Intent__c	Picklist	Package	TitanX → SFDC	Scoring job	High Intent, Low Intent or Bad Data
TitanX Last Signal Update	TitanX_Last_Signal_Update__c	Datetime	Package	TitanX → SFDC	Scoring job	Time of the last signal change. TBC
TitanX Enriched Phone 1–5	TitanX_Enriched_Phone_1__c … _5__c	Phone	Package	TitanX → SFDC	Enrichment job	Up to 5 new numbers. Separate from the 5 mapped phones
TitanX Enriched Phone 1–5 Signal	TitanX_Enriched_Phone_1_Signal__c … _5_Signal__c	Text	Package	TitanX → SFDC	Enrichment job	Signal for each enriched phone

Account and Opportunity

Object	Field label	API name	Type	Kind	Direction	Trigger	Notes
Account	TitanX Account Notes	TitanX_Account_Notes__c	Long Text Area	Package	TitanX → SFDC	Log & Finish	Notes written in Account Notes while working a contact
Account	TitanX Account LinkedIn URL	TitanX_Account_LinkedIn_URL__c	URL	Package	Both	Log & Finish
Account	Website, Industry, Number of Employees	Website, Industry, NumberOfEmployees	URL, Picklist, Number	Standard	Both	Log & Finish	Pre-mapped by default. Admin can change
Account	Any edited detail field	Mapped field	Varies	Standard or Mapped	Both	Log & Finish	Only fields shown in TitanX
Opportunity	Name, Stage, Amount, Close Date	Name, StageName, Amount, CloseDate	Text, Picklist, Currency, Date	Standard	TitanX → SFDC	Opportunity created in TitanX	TBC
Opportunity	Contact Role	OpportunityContactRole	Junction	Standard	TitanX → SFDC	Opportunity created in TitanX	Links the Contact to the Opportunity. TBC

Read from Salesforce

Object	Standard fields read	API names
Contact	First Name, Last Name, Title, Email, Lead Source, Phone, Mobile, Other Phone, Mailing address, Account, Owner	FirstName, LastName, Title, Email, LeadSource, Phone, MobilePhone, OtherPhone, MailingStreet, MailingCity, MailingState, MailingPostalCode, MailingCountry, AccountId, OwnerId
Lead	First Name, Last Name, Title, Email, Company, Website, Industry, Employees, Annual Revenue, Lead Status, Lead Source, Phone, Address, Converted fields, Owner	FirstName, LastName, Title, Email, Company, Website, Industry, NumberOfEmployees, AnnualRevenue, Status, LeadSource, Phone, Street, City, State, PostalCode, Country, IsConverted, ConvertedDate, ConvertedAccountId, ConvertedContactId, OwnerId
Account	Name, Billing address, Owner	Name, BillingStreet, BillingCity, BillingState, BillingPostalCode, BillingCountry, OwnerId
Opportunity	Name, Account, Stage, Close Date, Closed, Won, Owner	Name, AccountId, StageName, CloseDate, IsClosed, IsWon, OwnerId
User	Name, Email, Active, Created Date	Id, Name, Email, IsActive, CreatedDate
Task	Existing Tasks from the last 6 months	Imported once on the initial sync
All objects	System fields	Id, IsDeleted, CreatedDate, CreatedById, LastModifiedDate, LastModifiedById, SystemModstamp

Contact Details

Users can edit contact and lead details directly in TitanX. Edits to a contact sync to the corresponding Contact object in Salesforce, and edits to a lead sync to the corresponding Lead object.

When a user clicks Edit on the contact page, the contact details view opens and any field can be edited, as shown in the screenshot below.

Note: Phone numbers, signals, and intent cannot be edited here. Reps need to reach out to the admin to request changes to these fields.

After the user edits a field and saves (for example, changing the last name to 801), the change is synced to the matching field in Salesforce immediately.

Account Notes

While working a contact, the rep can write notes for the account that contact belongs to in the Account Notes section. These notes sync to that account in Salesforce, as shown in the screenshot below.

The notes are written to the TitanX Account Notes custom field on the Account object. Because they belong to the account rather than the contact, they are visible on the account record in Salesforce for every contact under that account.

Dialing

After a user makes a call in TitanX, they must log a disposition for it before the call can be logged. The call is logged in Salesforce as a call activity, and the disposition is synced along with it. If the disposition has a follow-up task, the task is logged in Salesforce as a task.

For instance, choosing the Not Now disposition requires a follow-up task, as shown below.

The call activity and its follow-up task are synced to Salesforce automatically once the user clicks Log & Finish. The task is created for the call in Salesforce.

Task mapping works one way only, from TitanX to Salesforce. Data captured during phone activity in TitanX is pushed directly to Salesforce Task records. The following fields sync to the call task:

● Subject

● Call duration

● Result (the disposition)

● TitanX Campaign Name

● TitanX Campaign Step Name

● TitanX Campaign Step Type

● TitanX Activity Source Phone (the number the call was made from)

● TitanX Activity Target Phone (the number that was dialed)

● TitanX Activity Phone Type

● TitanX User (the rep who made the call)

Users can also take notes during a call in TitanX. After they click Log & Finish, the notes appear on the call activity in Salesforce as shown below.

In Salesforce:

Users can also change a call’s disposition after it is logged. When they do, the previously created follow-up task is deleted and a new one is created if the new disposition requires it. Users don’t need to delete the old task manually in either TitanX or Salesforce, because the change is applied in both at the same time.

Job Submission and Scoring Outputs

When a user submits a job in TitanX, the scoring results are written back to Salesforce. This happens on both Contacts and Leads, depending on which objects they are scoring.

Each phone number mapped during setup is paired with its own signal field, for example Phone and Phone Signal, Mobile and Mobile Signal (up to 5 phones can be mapped). Signals populate in Salesforce as soon as scored data is returned.

TitanX also writes four final evaluation fields, all of which are required:

● TitanX Best Phone

● TitanX Best Phone Signal

● TitanX Last Signal Update

● TitanX Intent

TitanX Best Phone always points to the phone number with the highest current score. If a phone’s score changes, the field updates automatically to point to the new best phone.

Enriched Phones

When enrichment is enabled, TitanX returns up to 5 enriched phone numbers for a record and writes them to Salesforce along with a signal for each:

- TitanX Enriched Phone 1 through TitanX Enriched Phone 5

- TitanX Enriched Phone 1 Signal through TitanX Enriched Phone 5 Signal

Enriched phones do not count against the 5 standard phones used for scoring. LinkedIn URL is used as the matching field for enrichment.

SFDC field Schema- Sync with TitanX