dbc066eff3774598b82bc9c43bcbd3a2Q: Technical Questions
1) How does Lead Scoring in Dale work?
2) In general, how does gating (opt-in) work and what Unique ID (UID) options are available (cell # / email)?
2A) Do you offer One Time Password (OTP) functionality for cell # / email gating purposes in order to reduce “fake” emails / cell #’s ie SPAM?
(e.g., when gating by cell # / email, they must enter the 6 digit code sent to them before advancing in the demo)
3) For a “medium” length branched demo, at what point in the flow should we ask for their email address? Based on aggregate usage analytics, what have you found has the optimal (highest) conversion rate?
4) Can you give me some Use Cases for what I’d use your API for?
5) Noticed Dale is built on WP & loaded slow on mobile (iPhone17, Safari)for me. Curious why WP vs newer technologies?
6) Timeframe for MCP Server?
nizamdale
Aug 20, 2026A: 1) Lead scoring: Automatic, based on engagement. Weights intent over fit (~70/30) with a recency decay. Signals: topic selections, watch depth, replays, heatmaps, downloads, CTA clicks. Pushes into HubSpot/Salesforce. Live on limited accounts, rolling out shortly.
2) Gating and UID: Captures name, email, custom fields. Invited or bulk-imported contacts get a unique link that IDs them with no prompt; for public links, the email they enter is the identifier. You may build a form to request deletion if necessary
2A) OTP verification: Not available today. Sensible anti-spam ask - logging it for the pipeline.
3) Where to ask for email: I won't quote a benchmark I can't verify. The principle: anonymous exploration doesn't cost you a contact, so let them explore the branch and some content first, then gate the higher-value asset or CTA once interest is shown. Build up the curiosity, first 3 minutes is very important, you may then ask
4) API use cases: Auto-invite a user to a personalized demo on signup (invite-users endpoint); pass name/company for auto-fill via dynamic variables; trigger demo links from your automations or an AI SDR; catch engagement events via webhooks to trigger follow-ups or sync to your systems.
5) WordPress / slow load: The marketing site (getdale.com) and the app (app.getdale.com) are separate stacks - WordPress is only the marketing site, not the demo engine. If a demo loaded slowly, send me the URL and device and I'll get it checked (load also depends on media weight).
6) MCP timeframe: There are a lots in the pipeline. It's actively planned (AI assistants pull your demo insights, contacts, analytics, plus invite-to-demo). If it's a deciding factor, tell me what you'd connect it to - our live API and webhooks may cover it today.
Happy to walk through scoring and gating on a call: https://getdale.com/free-consultation/