Your client’s knowledge, on their site
Connect each website to its own Snakk agent with relevant information about the client’s services and procedures. Check that connection whenever you clone or transfer a Duda site.
SNAKK + DUDA · FOR AGENCIES
More client sites. An AI agent for each.
Let visitors type or talk to an AI agent on your client’s Duda website. Your agency sets up the connection, and the client’s own information guides the answers. Start with one site, test the experience, then take what you learn to the next client.
A choice of chat or voice
The integration kit gives visitors one place to choose text chat or browser voice. Voice requires a separate start action and microphone permission. You choose which channels to offer.
A process you can repeat
The local configuration tool creates an embed for one website at a time. For several client sites, a technical generator can produce a separate code block for each. Every site still needs its own configuration, publishing and checks.
ONE CONNECTION PER CLIENTIllustration
- EXAMPLE 01Workshop
Services and opening hours
Agent 01Chat + voice - EXAMPLE 02Estate agent
Services and enquiries
Agent 02Chat + voice - EXAMPLE 03Consultancy
Expertise and contact routes
Agent 03Chat + voice
FROM ENQUIRY TO NEXT STEP
How Snakk fits with Duda
EXAMPLE · DEPENDS ON YOUR SETUP
A visitor opens Snakk on your client’s website and chooses chat or voice.
The agent responds using the information and instructions you have configured in Snakk.
Agree what the agent should do when it cannot answer. Booking, CRM and other system actions require separate configuration and testing.
EXAMPLE · DEPENDS ON YOUR SETUP
Choose one client and a focused task, such as answering questions about services and opening hours.
Connect the correct agent to the site and test on the client’s published HTTPS domain.
Repeat the checklist for the next client, with a separate agent, content and domains. Always check the mapping again after cloning a site.
PRODUCT VIEW
A closer look
A PRACTICAL START
Set up Snakk for Duda
Prepare a Snakk account and an active agent for the client. Add their knowledge and enable chat, browser voice or both.
Use the local configuration tool to enter the Duda site ID, the client’s public Snakk agent ID, language, position and exact HTTPS domains. Configure the domains in Snakk as well.
Remove previous Snakk embeds. Paste the complete code block into Duda’s Body End HTML, usually under Settings → Head/Header HTML. Preserve any other code on the site.
Save and republish. Test the published site on mobile and desktop, using a keyboard and with microphone access both granted and denied. The kit is deliberately inactive in the editor and preview.
Agree who will maintain the client’s information and handle issues. To remove the kit, delete its code block and republish; this does not delete past conversations in Snakk.
Duda
Useful answers
Is Snakk available in the Duda App Store?
This delivery is a manual integration kit in development, not a published App Store app. The kit has been built and tested locally with simulated conversations. Testing on a real Duda website is still outstanding. Duda approval and commercial terms have not been confirmed.
Can our agency use it across several client sites?
The kit produces a separate configuration for each website. Use a separate agent for each client site and check the client, account, agent and domains. This delivery does not include automatic rollout or central management within Duda. Snakk agreements and access need to be arranged for your clients.
What should we check when cloning a Duda site?
A copied site may include the embed code. Remove or replace it before publishing the new site. Check the site ID, client, agent and allowed domains so the new site does not use the previous client’s configuration.
Can we offer this under our own brand?
Branding, resale and a client portal must be agreed separately with Snakk. Duda’s white-label features and subscription do not automatically grant rights to Snakk. This page does not promise a particular partner status or white-label package.
Does this integration answer phone calls too?
No. Browser voice is a conversation on the website using a microphone. AI phone answering is a separate Snakk service with its own setup. The embed does not provision a phone number or call forwarding.
What does it cost?
The integration code has no separate installation fee. A Snakk account and any paid services or usage are additional, as is your client’s Duda subscription. Setup support and agency agreements are arranged separately.
YOUR NEXT STEP
Explore Duda with Snakk
Manual integration kit in development. Tested locally; verification on a real Duda website is still outstanding. No published App Store app.
Snakk is an independent service. Duda names and logos belong to their respective owners. Their use here identifies the platform and does not imply endorsement.