Separate business accounts
Keep client operations organized by account. Access is checked against account membership and the permissions required for the action.
Review account organizationControl around the conversation
Call data deserves clear boundaries.
Decide who can access information, how long it stays useful, and where it can go. Understand the controls before you put a workflow into practice.
People, accounts, and access
Give access a purpose.
A person reviewing campaign performance does not necessarily need to change routing, manage payments, or listen to every recording. Lead Source uses account membership, roles, and permissions to control the work a person can perform. Client accounts give agencies a structure for keeping business records in the right context.
Account separation still depends on deliberate administration. Invite people to the accounts they need, review permissions when their responsibilities change, and remove access when the relationship ends. Use specific partner access for the parts of a call business that external partners should see.
Role-based permissions
Distinguish reviewing information from changing it. Assign access around the person's responsibilities instead of sharing an administrator login.
Review team permissionsRecording access
Treat recordings and transcripts as sensitive business information. Restrict who can review them and check the access assigned to connected workflows.
Review recording workflowsThe information lifecycle
Collect deliberately. Review carefully. Retain for a reason.
-
Choose what you need
Define the purpose of recording, transcription, and conversation analysis. Apply the account and campaign settings that match that purpose.
-
Limit who can review it
Check account roles, recording permissions, and partner access. Revisit them as teams and client relationships change.
-
Set retention expectations
Recording and transcript retention can be configured separately. Applicable holds and the effective policy affect processing and removal.
-
Check the information that leaves
Review exports and connections before sharing data. The receiving system has its own access, retention, and handling responsibilities.
Controls with a defined scope
Understand what each setting does.
- Retention
- Recording and transcript policies define how long those materials should be retained. Processing depends on the effective policy, applicable holds, and the configured retention workflow.
- Text redaction
- Supported phone numbers and email addresses can be masked in transcript text. Automated redaction can miss information and does not remove speech from the original audio.
- Connection credentials
- Account API keys support controlled custom connections and can be revoked. Treat every key as a credential and review the access needed by its purpose.
- United States calling
- Lead Source's calling and messaging workflows are restricted to United States numbers. International calling is not part of this product offering.
Evaluate your requirements
Bring the questions your business needs answered.
For a security review, describe the information you expect to handle, who needs access, the retention period you require, and the systems that need to receive records. Specific requirements make it possible to assess the actual workflow rather than rely on a general label.
This page explains product controls. It is not a certification statement or a substitute for your organization's review. Ask the team to confirm any contractual, hosting, data-location, or industry-specific requirement before using the product for that purpose.
Frequently asked questions
A few more things, explained.
Explore the details. Open a question for the answer.
What does Lead Source's security overview cover?
It explains account access, recording permissions, retention, transcript redaction, and connection controls. The page helps you prepare questions about your specific data-handling requirements.
How are separate clients organized for data access?
Businesses can use separate accounts with their own memberships and permissions. Administrators should review the active account and the access granted to each teammate.
Does every teammate need administrator access to review calls?
No. Access should match the person's work. Use roles and permissions to distinguish reviewing call information from changing settings or managing other parts of an account.
Can recording review be treated separately from general account access?
Recording access is subject to permission checks. Review the role and scope assigned to each person rather than assuming that access to one part of an account grants access to all its audio.
Can recording and transcript retention periods differ?
The retention policy supports separate periods for recordings and transcripts. Confirm the effective policy and the processing workflow that applies to the account or campaign.
Do retention settings override an applicable hold?
Applicable holds affect retention processing. A retention period alone should not be interpreted as a promise that all related data is immediately removed in every circumstance.
Does transcript redaction remove sensitive speech from audio?
No. Text redaction and audio are separate. Masking supported information in a transcript does not erase the same information from the recording.
Can automated text redaction find every private detail?
No. Supported patterns, including phone numbers and email addresses, can be masked, but automated detection can miss information. Review the output before sharing it.
How should a team handle downloaded call reports?
Limit exports to the information needed and store them where the right people can access them. A downloaded copy needs its own retention and sharing controls outside Lead Source.
What happens to access when a custom connection is retired?
Revoke the account API key used for that connection and review any copies already sent to the receiving system. Ending access does not automatically delete information held elsewhere.
Does this security page claim an independent certification?
No. It describes product controls and does not claim an audit certificate or industry-specific compliance status. Confirm any required assurance directly with the team.
Can I assume a particular hosting location from this overview?
No. Hosting, data-location, and contractual requirements need explicit confirmation for your evaluation. Do not infer them from the availability of a data-control feature.
Does access to Lead Source authorize recording every caller?
No. Account access and recording permissions are product controls. Your organization remains responsible for deciding when recording is appropriate and meeting applicable requirements.
What should I include in an initial security inquiry?
Describe the general concern or requirement and how the team can contact you. Leave out private caller information, recordings, passwords, and connection credentials.
What should a larger team review before using call data across tools?
Map which people and systems will receive the data, what each needs, and how long each will keep it. Confirm the available controls and responsibilities at every destination.
Meet your next growth tool
Start with the requirements that matter to you.
Tell us about your team's access and data-handling needs before you choose a workflow.