Kassie

Company and category

Company

Kassie AI, Inc.

Founder

Raphael Chi

Category

Inbound AI SDR

Target customer

B2B companies that want to turn relevant website traffic into qualified pipeline. Fit depends on the company’s website demand, buyer needs and sales process, rather than whether it operates in technology or software.

Product workflow

1. A website visitor starts a conversation.
2. Kassie answers from approved knowledge.
3. She learns company, use case, urgency, and fit.
4. She advances or disqualifies the opportunity.
5. Qualified prospects book with sales.
6. Sales receives the conversation and qualification context.
7. The customer measures the opportunity in Kassie Workspace.

Commercial facts

Growth starts at $1,000 per month, billed annually ($12,000 per year, paid upfront), or $1,500 per month, billed monthly. Both options include the same product and services. Enterprise pricing is custom.

Most customers can go live in 3 to 5 business days once the required access and approvals are available. We handle knowledge setup, qualification design, integration configuration, booking tests, and website deployment.

Integrations

• HubSpot: Send qualified visitor and conversation context to HubSpot.
• Salesforce: Send qualified visitor and conversation context to Salesforce.
• Google Calendar: Connect Google Calendar to Kassie.
• Outlook Calendar: Connect Outlook Calendar to Kassie.
• Calendly: Let qualified visitors book the right Calendly meeting from the conversation.
• HubSpot Meetings: Connect HubSpot Meetings to Kassie.
• Cal.com: Connect Cal.com to Kassie.
• Slack: Send configured Kassie notifications to the right Slack channel.
• Microsoft Teams: Send meeting, sales-accepted, and closed-won updates to your team’s Microsoft Teams channel. Standard channels. Configured during onboarding.
• Email: Receive configured Kassie notifications by email.

Choose either Slack or Microsoft Teams for channel notifications.

Security summary

Kassie protects customer information through controlled access, customer data separation, and encrypted integration credentials.

• Controlled workspace access: Kassie Workspace requires authenticated access. Permissions determine who can view and manage customer information and settings.
• Customer data separation: Customer data access is scoped to the appropriate workspace, with server-side checks enforcing those boundaries.
• Protected integration credentials: Credentials for supported integrations are encrypted before storage and handled on the server.
• Authorized connections: Your team chooses which systems to connect and authorizes the permissions needed for those integrations.

Published writing / Knowledge corpus