Getting Started

Get started with a free trial today and see your agentic conversion grow.

What You Configure

Item	What it controls
Website domain	The public site where agents should discover actions.
Action	The task an agent can run, such as Book Demo.
Fields	The inputs Teckel must collect before the action can run.
Destination	Where Teckel sends completed requests, such as HubSpot, Salesforce, Calendly, Slack, email, or a webhook.
Install	The pointers agents use to find the Teckel Action Registry on your website.

1. Create Or Choose An Organization

Create an organization for your company. This is where you manage team access, billing, and domain configurations for your websites.

2. Configure Your Site

Add your website domain. Teckel creates a workspace for you to manage the Action Registry and track visiting agent activity.

3. Add One Action

Choose a task that already has a clear owner.

Good to consider first actions:

• Book Demo
• Start Trial
• Request Quote
• Share Feedback

These are actions the agent sees and can invoke like tools or skills.

4. Connect The Destination

Choose where the action should go.

Team	Typical destination
Sales	HubSpot, Salesforce, Calendly, Slack, email
Support	Zendesk, Intercom, Slack, email
Operations	Webhook, Slack, email

Use your own system of record, via our current integrations (more to come) or with webhooks.

5. Set Required Fields

Tell the agent the needed fields to complete the action.

For a demo request, start with something like:

• Name
• Email
• Company
• Optional message

6. Install Teckel on Your Website

Add Action Registry pointers to your public website.

<script
  src="https://cdn.teckel.ai/agent-ready.js"
  data-site-id="site_abc123"
  data-action-registry-url="https://app.teckel.ai/registry/site_abc123.json"
  defer
></script>

Install with a prompt in 5 minutes or less.

7. Verify

Run the readiness check after the deploy.

Teckel checks that:

• The SDK loads on the page.
• The Action Registry is reachable.
• Published actions can be discovered.
• Required fields appear in the action schema.
• The selected website pointers are installed.

8. Review Activity

Use Activity to see when agents read the Action Registry, call an action, and what they share all in one place for audit history.