— INTEGRATION · SALESFORCE · CONNECTED APP

Cyborgs that drive the funnel in Salesforce.

Sales Cyborg works leads, qualifies, follows up, drafts proposals. Customer Support Cyborg works cases. All inside your Salesforce instance, under a dedicated Connected App.

Editions supported

Sales Cloud + Service Cloud, Professional / Enterprise / Unlimited / Performance editions. Marketing Cloud + Pardot are roadmap (v0.3.x).

— 02 / CAPABILITIES

— WHAT THE CYBORG CAN DO IN SALESFORCE

Capabilities · scoped, audited.

CAP · LEADS

Lead capture + qualify

Imports inbound leads, dedupes, qualifies via your custom fields, schedules follow-up activities.

  • Dedupe across leads + contacts
  • Qualification scoring
  • Activity scheduling
  • Lead conversion to Opp
CAP · OPPS

Opportunity movement

Updates opp stages, log activities, drafts proposals, attaches collateral, posts Chatter updates.

  • Stage transitions
  • Activity logging
  • Proposal drafting
  • Chatter updates
CAP · CASES

Cases + SLAs

Triages incoming cases, drafts replies, escalates per SLA, manages case queue.

  • Case triage + routing
  • Reply drafting
  • SLA tracking
  • Knowledge article suggestions
CAP · REPORTS

Reports + dashboards

Reads existing reports, posts pipeline summaries, flags risk deals to managers.

  • Read reports
  • Pipeline summaries
  • Risk-deal alerts
  • Forecast updates

03Auth + scopes.

  • Connected App · we install a managed package “A’nil Cyborg” with our public PKI; you approve the install in your org.
  • OAuth 2.0 with PKCE · the Cyborg authenticates as a dedicated cyborg-svc user in your org. Refresh tokens rotate.
  • Profile-scoped · the cyborg-svc user gets a profile you control (e.g., custom “Cyborg Sales” profile with field-level security per object).
  • Field-Level Security enforced — if your profile blocks a field, the Cyborg cannot read or write it.

04Setup · 15 minutes.

  • Step 01 · Install A’nil Cyborg managed package from AppExchange.
  • Step 02 · Create a dedicated cyborg-svc user with a custom profile (we provide a template).
  • Step 03 · Assign FLS, sharing rules, role hierarchy slot.
  • Step 04 · Authorise the Connected App with PKCE flow from Cyborg dashboard.
  • Step 05 · Test with a single lead/opp; observe in Field History Tracking.

05FAQ.

Field History Tracking + audit?+

Every Cyborg action shows up under the cyborg-svc user in Field History + Setup Audit Trail. Combined with our own audit log: dual record.

Custom objects + Apex?+

Custom objects supported automatically. Apex triggers / validations are honoured (the Cyborg gets the same validation errors a human user would).

API call limits?+

The Cyborg uses Bulk API for batch ops + REST for transactional. We monitor your daily API limit and back off when it’s under pressure. Enterprise customers can request dedicated Connected App for separate quota.