Dashly

Three language model agents carry the inbound workflow: the Qualifier asks ideal customer questions and marks qualified leads, the Support agent answers from the knowledge base through retrieval, and the Booking agent schedules inside the conversation. Each has a defined job and hands off to the next. Remove them and a full conversational marketing platform remains, with live chat, triggered messages, a team inbox, email campaigns and a customer data platform.

The agents converse, qualify, answer and book without a person in the loop, passing only qualified leads to the sales team, and nurturing reminders run with no manager time required. Agents hand conversations to each other rather than to a human by default. Limits on what the Support agent may promise about pricing or product, review of agent conversations, and how an agent is paused when it misbehaves are not described.

OpenAI is named as the current provider of language model inference and retrieval for the agents, with Pinecone holding the vectors derived from customer content, both processing in the United States. Qualification follows the customer's own ideal customer questions rather than a score. Whether visitors are told they are talking to an AI agent is not addressed, and a no branding add on removes Dashly mentions from chat and email.

WOWInfluencer, a marketing technology company with 150,000 monthly visitors, reports a 653 percent return on marketing spend in one quarter, 82 percent of qualified leads converting to confirmed meetings and 1.6 sales roles freed. An unnamed European real estate platform doubled lead to qualified conversion from 38 to 76 percent. A quarterly funnel table counts 470 contacts stage by stage with pipeline by scenario. Whose funnel that table measures is not stated, and headline claims such as 99.6 percent faster first response carry no basis.

Customers can set up consent collection in pop ups and chat before capturing email addresses, phone numbers or other personal data, and the customer decides how the data is used. Reminders and follow ups travel over email, WhatsApp and Telegram. Unsubscribe handling, WhatsApp opt in rules and email marketing law are not addressed by name, leaving lawful messaging to the customer.

Dashly processes customer data as a processor on the customer's written instructions and offers a signed DPA on request covering security, subprocessors, data subject requests, breach notice, deletion and return, audits and US state privacy law. Transfers rely on the 2021 standard contractual clauses and the UK transfer addendum, and the subprocessor list shows each provider's location with 30 days' notice of changes. Deidentified data used to improve the service is never reidentified. The DPA itself is not public.

The lead profile is built from data the customer collects: site behavior from its own tracking script, fields synced from its CRM, conversation history and leads uploaded through the API. Dashly sells no contact database of its own, so the provenance question reduces to the customer's own collection. Third party account data enters only when a customer connects an integration such as Facebook or Zoom, and Zoom contributes only a meeting status identifier.

Collection runs from a script on the customer's own site, and CRM, calendar and analytics connections use their native interfaces. Messaging reaches WhatsApp, Telegram and Instagram through integrations, with a Facebook bot in early access. How those messenger connections are made, and whether they run on the official business interfaces each platform requires, is not stated.

Data is processed only on the customer's instructions, and aggregated or deidentified data may be used to improve the service under a commitment never to reidentify it or combine it with outside data. Whether customer conversations or knowledge base content train models, at Dashly or at OpenAI, is not addressed, and retention terms for agent prompts and outputs are not given. Customer data is logically separated, with physical separation available as a private cloud.

Website visitors meet agents that open with personal context, such as pages viewed and earlier questions, and the demo labels the speaker as a Dashly agent. Whether that label stays once the no branding add on is active, and whether agents state they are software, is not described. Dashly takes no position on Article 50 of the EU AI Act.

HubSpot, Salesforce, Pipedrive and amoCRM connect as CRMs, and CRM fields feed the lead profile the agents read before replying. Booking runs through Google Calendar, Calendly or Cal.com, events pass to Mixpanel, and custom webhooks and an API for uploading leads cover the rest. Field mapping, sync direction and conflict rules for each CRM are not described.

Customer content is hosted on Google Cloud in the United States, vectors sit with Pinecone in the United States, and email goes through Mailgun, while a global content delivery network serves each request from a point near the user. Data is logically separated at the application level, and a private cloud deployment with physical separation is available on request. Hosting outside the United States is not offered.

A detailed security policy describes TLS 1.2 or higher in transit, AES 256 at rest with encrypted backups and annually rotated keys, VPN and named SSH key access to infrastructure, severity based incident response starting within one hour for critical issues, and a 12 month audit log in the product. Dashly holds no SOC 2 report or ISO certification, and no third party audit of these controls is offered.

For up to 1,000 monthly visitors, Conversation costs $39, Support $79 and Marketing $109 a month, or $31.20, $63.20 and $87.20 on annual billing, with unlimited seats and a 7 day trial. Visitors above quota are billed per visitor at a rate for each plan, extra email costs $0.03 a message, and add ons such as no branding ($15) and a welcome bot ($29) are priced. The AI bot, sold only on Support and Marketing, starts at $60 a month and rises with query volume, so the agent bill depends on usage.

Dashly exports, corrects or deletes contact data on the customer's request, the DPA covers deletion and return of data at the end of service, and a 12 month audit log records exports and bulk operations. Subscriptions renew for one month or the prior term, whichever is shorter, unless either side gives 30 days' notice, and payments are non refundable. A self service export of the full lead profile and conversation history is not described.

Email leaves through Mailgun, each plan carries an email quota with overruns billed per message, and the no branding add on lets a customer send from its own domain. Messages go mostly to inbound leads who started a conversation, plus booking reminders. Warmup, authentication setup, complaint monitoring and response to falling sender reputation are not described.

Inbound focused B2B teams with meaningful site traffic are the target, typically software and services companies that want qualification and booking without an SDR team, and Dashly counts more than 70 of them as customers. WOWInfluencer and a European real estate platform carry the case evidence, while older stories come from education and fitness businesses. Supported languages for the agents and the geographic spread of customers are not broken out.