Salesforce integration for VYRA's sales follow-through
Give VYRA the approved Salesforce records needed for one qualified target, reply, or follow-through queue while the sales owner keeps claims and sending authority.
VYRA, the AI SDR, works from approved Salesforce account, contact, opportunity, and activity records to prepare qualified targets, stage outreach, route replies, and keep the next follow-through visible. The first accepted result is a checked sales queue: the account and contact, fit evidence, last activity, proposed message or follow-up, proposed record change, exception, and owner decision.
This is for a small sales team that treats Salesforce as the current pipeline record. It replaces manual record gathering, first-draft writing, and routine activity cleanup for the approved workflow. The owner still decides audience, exclusions, claims, sending, material replies, customer commitments, and consequential stage changes.
Which Salesforce records does the workflow use?
Approve objects and fields because the result needs them. Do not grant “Salesforce access” as an undifferentiated block.
Salesforce object and operation record
The engagement replaces these examples with the exact Salesforce environment, object names, fields, and operations.
| Record | Approved use | Possible operation when recorded | Owner boundary |
|---|---|---|---|
| Account | Company identity, fit facts, territory, owner, exclusions | Read; propose or apply approved hygiene fields | Owner approves targeting and material account changes |
| Contact | Approved person, role, relationship, consent or exclusion status | Read; propose or apply approved contact fields | Owner controls audience and privacy decisions |
| Opportunity | Stage, value, next step, close timing, decision owner | Read; propose an approved next-step or stage update | Owner approves material stage, value, and commitment changes |
| Activity | Prior approved messages, meetings, calls, and follow-ups | Read; add an approved activity record after the event | External sending and material replies stay pending |
| Custom object or field | Only the specified business record required for acceptance | Exact read or write specified in the engagement | No assumption based on a similar standard object |
Deletion, bulk change, ownership transfer, workflow changes, and permission administration remain outside the public promise unless separately recorded and approved.
Salesforce calls these business records sObjects. Its REST API supports object metadata and record operations and a query resource. Those APIs describe what Salesforce can expose. VYRA's role and the engagement record determine which records and operations are actually used.
What does the first accepted result look like?
Suppose five replies arrived after an approved campaign. Two ask routine product questions, one asks for pricing outside the approved offer, one asks to stop contact, and one belongs to a different account.
From Salesforce record to checked reply queue
The work ends in an owner-readable result, not an invisible background update.
- 1
Resolve the record
Match each reply to the approved account, contact, opportunity, campaign, and prior activity. Leave uncertain matches unresolved.
Owner: VYRA
- 2
Check fit and exclusions
Confirm target criteria, consent or exclusion status, current product facts, and the last approved interaction.
Owner: VYRA
- 3
Prepare the response
Draft the reply, supporting evidence, next step, and any question that needs the sales owner.
Owner: VYRA
- 4
Stage the record change
Propose the activity, next-step, opt-out, or stage update and keep material changes pending.
Owner: VYRA
- 5
Accept in the work environment
Report the queue, conflicts, and held actions through Slack, WhatsApp, or Microsoft Teams as agreed.
Owner: Sales owner
The Microsoft Teams work-environment guide shows how a governed result and decision request can remain beside Microsoft 365 records. Slack supplies a shared-team view; WhatsApp supplies a compact owner brief. The selected environment does not change the Salesforce object or approval record.
How does Salesforce authorize API access?
Salesforce documents OAuth, an authorized app connection that avoids sharing the user's password, through an external client app. A successful authorization returns access and refresh tokens under the chosen flow. The Salesforce OAuth guide notes that the user must be authenticated and that multiple OAuth flows exist.
The app identity, integration user, profiles, permission sets, object rights, field rights, sharing rules, Salesforce environment policies, and selected flow all affect access. Do not infer that one user can expose every object or that a scope label overrides Salesforce record permissions. The engagement records the actual environment, identity, objects, fields, operations, and administrator.
API capacity is also specific to the buyer's Salesforce environment. Salesforce says most requests count against the organization's platform allocation and that limits can change. A fixed daily record volume would therefore be false. The role must handle limit or service responses as blocked or delayed work rather than silently skipping records.
What must a person approve?
The sales owner approves target rules, exclusions, message claims, campaign release, sending, material replies, and changes that affect forecast meaning or customer commitments. A privacy, legal, regulated, contractual, employment, or payment question routes to the relevant qualified person.
Technical approval belongs to the Salesforce administrator or delegated system owner specified in the engagement. Business approval belongs to the accountable sales owner. One person may hold both jobs in a small company, but the two decisions remain separate.
The current provider and data boundaries are on the security page. If Salesforce data appears in a Teams, Slack, or WhatsApp work surface, that destination and retention arrangement also need approval.
How do you test failure and revocation?
- Approved-object test. Read one harmless account and its approved fields. Done when: the queue cites the correct Salesforce record.
- Denied-field test. Request a nearby field outside the work record. Done when: no value appears and the role reports the boundary.
- Duplicate test. Supply two plausible contacts. Done when: VYRA asks for resolution instead of merging them.
- Write-hold test. Propose a material stage or value change without approval. Done when: Salesforce remains unchanged and the owner receives the decision request.
- Safe-write test. Use a disposable approved activity. Done when: only the specified field or record changes and the result links back to it.
- Limit test. Simulate a throttling or service response. Done when: the queue records the unfinished range and retry condition.
- Revocation test. Revoke the safe token or integration-user access. Done when: reads and writes stop and the agreed work environment receives a block.
What happens if the engagement ends?
Records written into the buyer's Salesforce environment remain there according to the buyer's Salesforce ownership and retention rules. Work delivered into Slack stays in the buyer's Slack. For Teams or WhatsApp, the account owner and channel-retention arrangement are stated before work begins.
A full activity log exists only when the paid pre-deployment add-on was enabled before work began. Internal role files and tests remain vendor-side, and no special FidelicAI export bundle is promised. What you own if you cancel has the full rule.
Questions buyers ask
Does VYRA read every Salesforce record?
No. The engagement names the Salesforce environment, objects, fields, record range, operations, and identity needed for the accepted result. Approved and denied tests verify that boundary.
Can VYRA update opportunities?
An approved engagement can name specific record operations. Material stage, value, ownership, forecast, or commitment changes stay with the sales owner unless a narrower standing rule is written and tested.
Does Salesforce OAuth grant access to every object?
No. OAuth is only part of the access decision. The integration user's Salesforce permissions, field rights, sharing rules, environment policy, and the operation itself still matter.
Does this work with every Salesforce edition?
API availability, allocations, identity options, and administration depend on the buyer's actual Salesforce edition, environment, and agreement. Verify them before access is approved.
How long does setup take?
Setup depends on the Salesforce environment, identity, object model, field rights, approval path, sample data, and acceptance tests. FidelicAI does not promise a five-minute connection or a fixed indexing period.
What happens when Salesforce returns a rate-limit error?
The role records the affected range, preserves finished independent work, follows the agreed retry route, and reports the block. It does not omit records and present the queue as complete.
Can VYRA send a reply because the CRM says the contact is active?
No. A CRM state is evidence, not sending authority. The owner controls audiences, claims, campaign release, sending, and material replies.
What should we approve first?
Approve one object set, one queue, one safe write, one denied field, one owner, and one revocation test. The first result should reconcile to Salesforce and leave consequential action visibly pending.
Follow the connected questions
Start and work together includes this decision and the questions that usually change it.
Which systems should an AI agent connect to?
Connect the smallest set of systems needed to read the source, write the work product, and preserve the record the business already uses.
Inspect supported integrations →What data should an AI agent be allowed to access?
Grant only the systems and records required for the role. Keep credentials, customer boundaries, logs, and approval rules explicit.
Where should an AI agent’s work appear?
Use the environment where the right people can see the result, inspect the source trail, correct it, and make the next decision.
What should you do next?
Copy the object table and replace each example with the buyer's exact Salesforce API name, field set, operation, owner, and deny case. Run the seven tests on safe records. Then choose VYRA's Day Pass, Sprint, or Monthly Retainer from the current rate board.
The AI agent buyer's guide gives the wider acceptance test. FidelicAI's product record supports the VYRA and Salesforce workflow; Salesforce sources support platform facts. Exact Salesforce environment compatibility, identity, limits, and record operations remain engagement-specific.
Sources
- Salesforce, OAuth and Connect REST API, accessed August 26, 2026.
- Salesforce, sObject basic information, accessed August 26, 2026.
- Salesforce, Query resource, accessed August 26, 2026.
- Salesforce, Connect REST API limits, accessed August 26, 2026.
- FidelicAI, VYRA, AI SDR, updated August 2026.