Retrieve information
For example status, availability or information a customer needs.
KNOWLEDGE, TOOLS AND SYSTEMS
Let the conversation
set something in motion.
Snakk can retrieve information, capture an enquiry and trigger follow-up in your systems. Start with the task, then agree the right connection.
FROM WORDS TO ACTIONS
Good conversations.
Connected to
your business.
From what the customer says to what your team needs. Snakk uses your business knowledge, clarifies the need and can pass the details to the system or person responsible for follow-up.
- Answer using the information you choose
- Run tasks through APIs and webhooks
- Give your team the context to take over
FROM SERVICE NEED TO FOLLOW-UP
- 01THE CUSTOMER GETS IN TOUCH“I need a service on Tuesday.”Phone · Chat
- 02
Understands what the customer needsBusiness knowledge + your instructions - 03API / WEBHOOKPasses the service enquiry onNeed · preferred time · contact details
- READY FOR YOUR SERVICE TEAMA clear enquiry to follow up.Your colleague confirms the appointment.
WHAT JOB NEEDS DOING?
From a question
to a concrete action.
Capture a need
Send agreed information from a conversation to the right recipient or system.
Booking and calendars
Help with an enquiry or reservation when access and the system support it.
Trigger follow-up
Send an internal notification, an agreed SMS or start a defined process.
ACCESS AND IMPLEMENTATION ARE DIFFERENT
Flexible connections.
Clearly scoped delivery.
Define the task
What should the AI read or do? Which responses and exceptions should the customer encounter?
Check interfaces and access
Available APIs, webhooks and permissions determine what is possible. Make or n8n can form part of the setup.
Build and test
You, your developer or Snakk builds the connection. Testing, responsibilities and future changes are agreed.
Webhook access is included in the pricing proposal. Custom connection work and external licences are separate costs. A system logo is not evidence of a ready-made integration.
FOR TECHNICAL TEAMS
Build further
with the API.
Explore documented access and bring the workflow you want to build. API access follows your account permissions.
Open API documentationREST API / SNAKK
GET /api/agents
X-API-Key: YOUR_TENANT_API_KEY
// Retrieve agents on the accountDocumented example. Keep API keys on your server. No code is executed here.
GOOD QUESTIONS
What is possible
for your business?
Can you connect to every system?+
Many systems can connect through APIs or webhooks. Actual access, interfaces and workflow need assessment before we confirm a specific implementation.
Do phone and chat share memory?+
Channels can use the same knowledge, instructions and tools. That does not mean a new chat automatically remembers a previous phone call.
Are SMS and BankID included?+
They are separate services. Messaging and identification are assessed independently; see the proposed SMS rate and request a BankID quote.
LET’S MAKE IT PRACTICAL
What would you
like help with?
A busy phone? The same questions in chat? Let’s start with one task you know well.
- We discuss what you need.
- You see a relevant example.
- We clarify the setup and next step.