Integration readiness

AI sales channels with the setup status and guardrails visible.

Review what Winrate can configure, what is guarded in beta, what is still roadmap, and what the product should not automate. The catalog covers lead sources, email, voice, billing, webhooks, Telegram control, AI workers, and future CRM operations.

Build your Sales BlueprintReview trust controls

Catalog posture

Truth before automation scale

Provider groups7
Channel labels39
Rollout paths8 pilot with review gates, 7 configure for rollout, 3 validate roadmap fit, 1 no rollout path
Public stanceConfigurable, guarded, roadmap, or explicitly unsupported

Revenue-safe rollout paths

Each status maps to a commercial next step, so evaluation can move toward revenue without turning roadmap or prohibited behavior into a sales promise.

Claim-safe buyer routing
Configurable

Configure for rollout

Validate deployment secrets, provider account ownership, budget, suppression, and approval gates before live use.

Configurable does not mean active in every workspace; production behavior depends on server-side setup.

Guarded

Pilot with review gates

Use a bounded pilot with operator review, mock/configured-mode clarity, and explicit launch blockers.

Guarded beta flows should not be described as autonomous provider execution or guaranteed conversion.

Roadmap

Validate roadmap fit

Qualify buyer demand, revenue impact, support cost, compliance posture, and implementation sequence before committing.

Roadmap capabilities are not live product behavior and should not be sold as available today.

Boundary

No rollout path

Use this row as a sales and product boundary; route buyers toward compliant review-only alternatives.

This capability is intentionally unsupported unless product, legal, security, and platform policy change.

7

Configurable

Can move to configured mode when deployment-side secrets and checks are present.

8

Guarded

Available as a reviewable foundation, mock-backed flow, or limited beta surface.

3

Roadmap

Planned expansion that should not be sold as live product behavior yet.

1

Boundary

Explicitly excluded from the product stance and public sales claims.

Channel and provider matrix

Each row separates current behavior from setup needs and future expansion so sales, product, and implementation teams do not overpromise.

Human approval remains the default gate for risky actions

Lead-source discovery

Source planning, evidence capture, and reviewable lead discovery before any outbound action.

3 entries

Website and site-signal research

Turns a workspace website and Sales Blueprint context into reviewable source-run evidence.

websitelead source
Request beta rollout

Status

Guarded beta

Commercial path

Pilot with review gates

Guarded beta flows should not be described as autonomous provider execution or guaranteed conversion.

Current mode

Mock-backed source adapter records candidates, dedupe posture, quality score, evidence, rejection reasons, and next action for review.

Required setup

  • Business website and ICP context
  • Workspace regions, buyer roles, and disqualifiers
  • Production crawler provider before live-scale sourcing

Guardrails

  • Lead quality scoring
  • Rejected-lead tracking
  • Suppression-aware dispatch before outreach

Search intelligence

Uses search-channel planning to retain evidence signals and expose discovery quality before outreach.

searchlead source
Request beta rollout

Status

Guarded beta

Commercial path

Pilot with review gates

Guarded beta flows should not be described as autonomous provider execution or guaranteed conversion.

Current mode

Mock-backed search intelligence is available for planned source workflows and dashboard review.

Required setup

  • Search keywords from the Sales Blueprint
  • Target segments and regions
  • Production search/data provider with terms-aware usage controls

Guardrails

  • Evidence snippets retained for review
  • Readiness gaps before weak plans scale
  • No universal search scraping claim

Directory research

Prepares commercial directory source runs with rejection reasons and source-quality review.

directorylead source
Request beta rollout

Status

Guarded beta

Commercial path

Pilot with review gates

Guarded beta flows should not be described as autonomous provider execution or guaranteed conversion.

Current mode

Mock-backed directory adapter supports source planning and review without claiming live directory harvesting.

Required setup

  • Directory source selection
  • Qualification rules and exclusion rules
  • Approved provider terms for production directory data

Guardrails

  • Rejected reason groups
  • Quality score visibility
  • Operator review before campaign creation

Outreach delivery

Email and social-style outreach surfaces with explicit approval, suppression, and provider checks.

3 entries

Resend email delivery

Sends approved email outreach through Resend when deployment secrets and sender identity are configured.

emailoutreach
Request rollout review

Status

Configurable

Commercial path

Configure for rollout

Configurable does not mean active in every workspace; production behavior depends on server-side setup.

Current mode

Configured dispatch uses Resend API keys after campaign approval, suppression checks, and usage checks; otherwise it queues in guarded mode.

Required setup

  • RESEND_API_KEY
  • RESEND_FROM_EMAIL
  • Approved sending domain and sender reputation controls

Guardrails

  • Owner/admin approval before dispatch
  • Suppression check before provider delivery
  • Idempotency key per campaign activity

SMTP-owned sender path

Tracks an app-owned SMTP readiness path without asking users to paste raw provider secrets into the browser.

emailoutreach
Request beta rollout

Status

Guarded beta

Commercial path

Pilot with review gates

Guarded beta flows should not be described as autonomous provider execution or guaranteed conversion.

Current mode

Readiness depends on deployment-side SMTP configuration; public copy should not imply every SMTP relay is production-ready.

Required setup

  • SMTP_HOST deployment configuration
  • Domain authentication and bounce handling plan
  • Provider-specific production send implementation review

Guardrails

  • Deployment-side setup only
  • No browser-entered raw secrets
  • Approval and suppression gates before live sending

LinkedIn-style outreach review

Supports review-only social outreach drafting posture; it does not auto-connect or auto-DM leads.

linkedinsocial review
Request beta rollout

Status

Guarded beta

Commercial path

Pilot with review gates

Guarded beta flows should not be described as autonomous provider execution or guaranteed conversion.

Current mode

Mock adapter returns review-required status for LinkedIn-style outreach and keeps sending out of automation.

Required setup

  • Human operator review
  • Platform-policy review
  • Approved manual workflow outside automated dispatch

Guardrails

  • No automated social-platform sending
  • Review-required delivery status
  • Public claim boundary documented

Voice and meetings

Call dispatch and meeting conversion foundations that stay gated by review posture.

2 entries

Twilio voice calls

Dispatches reviewed voice calls through Twilio when credentials, TwiML, and callback setup are complete.

voicecall
Request rollout review

Status

Configurable

Commercial path

Configure for rollout

Configurable does not mean active in every workspace; production behavior depends on server-side setup.

Current mode

Configured Twilio calls require owner/admin action, verified email, usage budget, suppression checks, and call review posture.

Required setup

  • TWILIO_ACCOUNT_SID
  • TWILIO_AUTH_TOKEN
  • TWILIO_FROM_NUMBER

Guardrails

  • Call review posture
  • Suppression check before provider delivery
  • Twilio signature verification for status callbacks

Meeting conversion workflow

Schedules and tracks meetings from qualified leads, then records outcomes back into the workspace.

meetingsconversion
Request beta rollout

Status

Guarded beta

Commercial path

Pilot with review gates

Guarded beta flows should not be described as autonomous provider execution or guaranteed conversion.

Current mode

Manual meeting creation and outcome tracking exist; calendar-provider automation is still roadmap.

Required setup

  • Qualified accepted lead
  • Operator-owned meeting details
  • Future calendar provider configuration

Guardrails

  • Workspace-scoped meeting records
  • Won/lost conversion state
  • No claim of autonomous calendar booking today

Billing and webhooks

Subscription, provider-event, and lifecycle hooks that require deployment-side secrets.

5 entries

Stripe billing

Supports checkout, portal, cancellation, and subscription lifecycle events when Stripe secrets are configured.

checkoutportalbilling webhook
Request rollout review

Status

Configurable

Commercial path

Configure for rollout

Configurable does not mean active in every workspace; production behavior depends on server-side setup.

Current mode

Billing routes enforce owner/admin access, verified email, and webhook idempotency around subscription changes.

Required setup

  • STRIPE_SECRET_KEY
  • STRIPE_WEBHOOK_SECRET
  • Configured price mappings

Guardrails

  • Owner/admin billing authorization
  • Email verification required for billing mutations
  • Webhook idempotency records

Razorpay billing

Provides an India-friendly subscription path when Razorpay credentials and webhooks are configured.

checkoutsubscriptionbilling webhook
Request rollout review

Status

Configurable

Commercial path

Configure for rollout

Configurable does not mean active in every workspace; production behavior depends on server-side setup.

Current mode

Checkout and subscription webhooks are deployment-configurable and require signature verification.

Required setup

  • RAZORPAY_KEY_ID
  • RAZORPAY_KEY_SECRET
  • RAZORPAY_WEBHOOK_SECRET

Guardrails

  • Owner/admin billing authorization
  • Email verification required for billing mutations
  • HMAC webhook signature verification

Provider event webhooks

Verifies provider callbacks for email, billing, and voice lifecycle updates before applying state.

email eventsbilling eventsvoice events
Request rollout review

Status

Configurable

Commercial path

Configure for rollout

Configurable does not mean active in every workspace; production behavior depends on server-side setup.

Current mode

Resend, Stripe, Razorpay, and Twilio callback readiness depends on deployment-side webhook secrets.

Required setup

  • RESEND_WEBHOOK_SECRET
  • STRIPE_WEBHOOK_SECRET
  • RAZORPAY_WEBHOOK_SECRET

Guardrails

  • Signature verification
  • Provider event audit record
  • Idempotency or ambiguous-target protection

Contact intake notification

Alerts the team after a public contact or managed-services request is durably captured.

inbound intakeemail alert
Request rollout review

Status

Configurable

Commercial path

Configure for rollout

Configurable does not mean active in every workspace; production behavior depends on server-side setup.

Current mode

Contact requests are stored first; Resend notification is best-effort and depends on deployment-side sender and recipient configuration.

Required setup

  • RESEND_API_KEY
  • RESEND_FROM_EMAIL
  • CONTACT_INTAKE_TO_EMAIL

Guardrails

  • Durable capture before notification
  • Notification failure does not drop the request
  • Reply-to uses the buyer email for manual follow-up

Account lifecycle email

Delivers verification, password reset, and workspace invitation email when transactional sender secrets are configured.

email verificationpassword resetworkspace invites
Request rollout review

Status

Configurable

Commercial path

Configure for rollout

Configurable does not mean active in every workspace; production behavior depends on server-side setup.

Current mode

Production account email depends on deployment-side Resend sender configuration; missing configuration blocks invite creation instead of creating unusable invites.

Required setup

  • RESEND_API_KEY
  • RESEND_FROM_EMAIL
  • FRONTEND_URL

Guardrails

  • Short-lived hashed verification and reset tokens
  • Invite acceptance constrained to the invited email address
  • No browser-entered raw email-provider secrets

Command center

Telegram and AI-operator foundations for safe status checks and approval-gated proposals.

2 entries

Telegram command center

Lets a workspace bind Telegram for safe status, operator brief, sequence readiness, revenue forecast, deterministic aliases, and guarded pause request flows.

telegramcommand center
Request beta rolloutRead guide

Status

Guarded beta

Commercial path

Pilot with review gates

Guarded beta flows should not be described as autonomous provider execution or guaranteed conversion.

Current mode

Configured bot secrets enable read-only operator briefs, sequence-plan summaries, revenue forecast summaries, deterministic natural-language aliases, and approval-gated action proposals; Telegram does not approve campaigns, calls, billing, or provider changes.

Required setup

  • TELEGRAM_BOT_TOKEN
  • TELEGRAM_WEBHOOK_SECRET
  • Workspace chat binding by an eligible admin

Guardrails

  • Secret-header webhook verification
  • Hashed chat binding
  • Replay protection

AI worker operating plane

Registers AI workers, allowed tools, blocked tools, budgets, and approval-gated task proposals.

AI workercompany operations
Request beta rollout

Status

Guarded beta

Commercial path

Pilot with review gates

Guarded beta flows should not be described as autonomous provider execution or guaranteed conversion.

Current mode

The control plane shows worker posture and task proposals; autonomous external tool execution is not implemented.

Required setup

  • Workspace plan and budget posture
  • Allowed/blocked tool policy
  • Human review for high-impact task proposals

Guardrails

  • Worker permission lists
  • Budget blocking
  • Approval-inbox linkage

Operations roadmap

Future CRM, calendar, SMS, and company-management integrations that need deeper controls.

3 entries

CRM and calendar sync

Planned two-way sync for accounts, contacts, meetings, and deal handoff after the core workflow is stable.

CRMcalendarmeetings
Discuss roadmap fit

Status

Roadmap

Commercial path

Validate roadmap fit

Roadmap capabilities are not live product behavior and should not be sold as available today.

Current mode

The product tracks leads, meetings, and outcomes internally today; external CRM and calendar sync should be treated as roadmap.

Required setup

  • Provider OAuth and scopes
  • Field mapping and conflict strategy
  • Tenant-specific audit and rollback plan

Guardrails

  • Least-privilege OAuth scopes
  • Sync conflict review
  • Tenant-isolated mappings

SMS and messaging channels

Future outbound channels that require consent, regional compliance, opt-out handling, and provider-specific delivery controls.

SMSWhatsAppmessaging
Discuss roadmap fit

Status

Roadmap

Commercial path

Validate roadmap fit

Roadmap capabilities are not live product behavior and should not be sold as available today.

Current mode

The data model can describe SMS activity, but no mature SMS or WhatsApp product flow should be claimed today.

Required setup

  • Consent and opt-out model
  • Provider approval and templates
  • Regional compliance review

Guardrails

  • Suppression and unsubscribe enforcement
  • Channel-specific plan entitlement
  • Human approval for first live use

Company-management integrations

Long-term company operating-system ambition for low-risk operational workflows, not legal, finance, or employment decision automation.

HRERPfinanceoperations
Discuss roadmap fit

Status

Roadmap

Commercial path

Validate roadmap fit

Roadmap capabilities are not live product behavior and should not be sold as available today.

Current mode

AI worker foundations exist, but HR, ERP, finance, and broad company-management integrations remain roadmap.

Required setup

  • Explicit ownership and approval policy
  • Sensitive-data access controls
  • Provider-specific rollback and audit design

Guardrails

  • Human-owned legal, finance, and employment decisions
  • Least-privilege access
  • Action proposals before mutations

Policy boundaries

Capabilities Winrate should not market or automate unless the product stance changes.

1 entries

LinkedIn scraping and auto-DM

Winrate should not market browser scraping, auto-connect, or auto-DM behavior as supported product functionality.

LinkedInbrowser automation

Status

Not supported

Commercial path

No rollout path

This capability is intentionally unsupported unless product, legal, security, and platform policy change.

Current mode

Current LinkedIn-style behavior is review-only and mock-backed; platform automation claims are prohibited.

Required setup

  • No production setup path

Guardrails

  • Do not claim automated scraping
  • Do not claim auto-connect or auto-DM
  • Keep social outreach human-owned unless product policy changes

Integration expansion starts with the Sales Blueprint.

The safest path to advanced automation is to capture the business context first, then add channels only where setup, compliance, budget, and review controls are strong enough for real customer workflows.

Step 1

Capture ICP, offer, regions, goals, and disqualifiers.

Step 2

Review provider readiness, source evidence, and blockers.

Step 3

Approve live outreach only after suppression and entitlement checks.