Exploradorhigh priority
Prospect export with missing fields
Account, list, file and steps already provided.
makers support
Find help for the right product.
Access Makers support channels by product, find introductory resources and submit requests with enough context for a faster response.
triage by productThe right support for each product, without losing context.
choose the product
Start with the product to keep your request in context.
Each entry brings together the product page, the route to submit a request and service status guidance.
desktop · Linux x64
Bastidor
Local application for Linux x64: manage client work, deliverables, approvals and scope, with one main operator.
b2b prospecting
Explorador Comercial
Help with research, lists, enrichment, exports and organising sales opportunities.
assisted operations
AOS
Support for workflows, agents, tasks, approvals and operational coordination between Makers products.
bespoke software
Studio
Requests relating to projects, internal systems, dashboards, integrations, automations and continuous improvement.
customer service and sales
WhatsApp Agent
Help with conversations, human handover, qualification, assisted responses and operations on WhatsApp.
social commerce
Instagram Agent
Support for comments, messages, lead capture, social qualification and passing context to sales.
request types
Choose the category that best describes the issue.
A well-classified request reduces back-and-forth: the product, impact, steps to reproduce and relevant attachments help Makers route it more effectively.
Access difficulties
Login, permissions, account, environment or problems signing in.
Usage question
How to perform an action, interpret data or choose the next step.
Bug or unexpected behaviour
Something does not work as expected, fails, repeats itself or loses information.
Integration
Connections to systems, channels, forms, CRM, automations or data.
Billing
Plans, payments, documents, updating details or administrative requests.
Privacy and security
Personal data, access, confidentiality, permissions and legal requests.
how support works
Triage with context before routing.
Makers organises the request by product, issue type and impact. It then goes to the right team without losing the original history.
We receive the context
Product, account, description, impact, attachments and steps already tried.
We assign a priority
The request is classified as a blocker, question, fault, integration or administrative issue.
We route it to the product or team
Each product team receives the request with its history and the right category.
We follow through to resolution
The response keeps the context and explains the next step if information is missing.
quick resources
Before submitting a request, check the right resource.
docs
Documentation
Start with the product map and existing pages across the Makers suite.
startGetting started
Choose the product and go to its page for initial context.
faqFAQ
Identify the issue category before contacting the team.
releaseChangelog
Use the product status to put changes and behaviour in context.
statusStatus
Check the product status guidance in this support centre.
contactContact
Submit an administrative request or contact Makers through the general channel.
product status
Always identify the product when reporting status, changes or incidents.
This page does not promise an SLA or 24/7 availability. To report unexpected behaviour, include the product, environment, impact, frequency and evidence of the issue.
productWhich solution is affected?
impactIs the team blocked, or is it a question?
evidenceInclude a screenshot, example or steps.
next step
Could not find what you needed?
Submit an administrative request if the issue is not related to a specific product, or speak to Ada to route initial questions.