Sales employee
Configure qualification instructions, grounded product knowledge, handoff policy, and approved sales tools.
Configure, test, supervise, and govern AI employees for sales, support, and operations from a tenant-scoped workspace.
Configuration preview
Tool policies can require an authorized teammate to approve exact parameters before a write is executed.
Configure and supervise AI employees through persisted tenant data, explicit authorization, runtime gates, and auditable evidence.
Create tenant-owned employee drafts, publish immutable versions, and retain deployment evidence.
Attach bounded, scanned knowledge sources and retrieve source references through workspace policy.
Review tenant-scoped conversations, handoffs, messages, leads, and run evidence.
Apply tool policies and require authorized approval before governed write actions.
Enforce workspace roles, API scopes, commercial access, and entitlement limits.
Publish a workspace web-chat channel only when its runtime and commercial gates permit it.
Receive bounded channel events with identity resolution, replay protection, and rejection evidence.
Design and validate bounded workflow steps before production execution is approved and enabled.
Every employee moves through persisted configuration, governed data access, and reviewable runtime evidence.
Define the employee role, instructions, model policy, workspace ownership, and deployment targets in a persisted draft.
Attach approved knowledge, configure tool permissions, and require authorization for governed write actions.
Run controlled previews, review recorded evidence, and activate only the channels and runtimes that pass their gates.
Role templates accelerate configuration without bypassing workspace ownership, versioning, authorization, or review.
Configure qualification instructions, grounded product knowledge, handoff policy, and approved sales tools.
Configure support instructions, source-backed answers, conversation review, and human takeover rules.
Configure technical guidance, bounded knowledge retrieval, citations, and governed tool access.
This list is loaded from TEDLad's canonical provider registry. Connections and effects still require verified credentials, workspace authorization, and enabled runtime gates.
Slack
communication
communication
Microsoft Teams
communication
Discord
communication
communication
SMS
communication
Salesforce
crm
HubSpot
crm
Pipedrive
crm
Google Analytics
analytics
Mixpanel
analytics
Zapier
productivity
Effectful capabilities remain subject to workspace permissions, verified dependencies, launch acceptance, and explicit runtime gates.
Prices, capabilities, and limits are loaded from the same billing catalog used by Checkout and entitlement enforcement.
For small teams launching their first production AI workforce.
$499 / month
For scaling teams that need more employees, automation, and integration capacity.
$1,299 / month
For organizations requiring custom limits, security review, and service commitments.
Custom
Everything you need to know about TEDLad
Create an account, complete your organization and workspace setup, add approved knowledge, configure an AI employee, and validate it before deployment. Availability depends on the production services and provider credentials configured for your workspace.
TEDLad can use tenant-owned knowledge bases and documents that your workspace uploads and activates. Retrieval remains scoped to the organization and workspace, and content must pass the configured storage and malware-scanning boundaries before it becomes available.
TEDLad includes provider-specific connections for the integrations shown in the live integration registry. A connection is usable only after its complete credential bundle is encrypted, verified against the provider, and marked healthy. Each provider exposes only the read or write actions implemented for it.
Current plan names, prices, limits, and included capabilities are loaded from TEDLad's billing catalog on the pricing page. Checkout and subscription access are completed through verified Stripe events.
TEDLad applies tenant isolation, authenticated encryption for sensitive payloads, hash-only API credentials, bounded provider access, durable audit evidence, and fail-closed production controls. The security page describes the implemented controls and clearly distinguishes them from third-party certifications that have not been claimed.
Yes, subject to the active billing plan's AI-employee and usage limits. Each employee has its own versioned configuration, knowledge assignments, deployment targets, and operational evidence.