# Entagl

> Entagl helps businesses respond when a customer has a question, changes their plans or needs a person. Its AI customer service and sales platform uses the business information and permitted actions the owner chooses. Messaging, Voice AI, a shared inbox, CRM and booking tools support that work; availability depends on the product, setup and connected channel.

## Products
- [Receptionist](https://www.entagl.com/products/receptionist): AI for supported messaging workflows, including answering inquiries, qualifying leads, collecting information, and helping with bookings and sales.
- [Coordinator](https://www.entagl.com/products/coordinator): Voice AI for phone and WhatsApp customer service, sales, and booking workflows. The upcoming voice release supports natural interruptions and continued conversation while the AI checks details or handles permitted tasks. Recorded launch previews use fictional customers and example appointment data. Release availability depends on the workspace and calling connection.
- [Reputation Manager](https://www.entagl.com/products/reputation): Google review-reply management with supported owner rules, draft approval, location controls, and publication status. It does not remove someone else's reviews or automatically identify and call reviewers.
- [Studio](https://www.entagl.com/products/studio): Content creation for the business.
- [Ads Co-Pilot](https://www.entagl.com/products/ads-copilot): Advertising analysis and recommendations with approval controls.
- [Comments Agent](https://www.entagl.com/products/comments-agent): AI replies to supported social comments as part of the Receptionist offering.
- [Comments Automation](https://www.entagl.com/products/comments-automation): A separate comment-automation add-on with its own pricing and allowance.
- [Mirror](https://www.entagl.com/products/mirror): A visual-preview add-on for supported use cases.

## Customer service and sales capabilities
- [AI conversation controls](https://www.entagl.com/platform/ai-conversation-controls): A customer may send several messages, correct a detail or ask for a person. Configure how the AI handles those situations before they happen.
- [Cross-channel conversations](https://www.entagl.com/platform/cross-channel-conversations): Customers use different channels. Bring supported conversations and relevant customer information into Entagl so staff can see what they need before replying.
- [Shared team inbox](https://www.entagl.com/platform/shared-inbox): Open the conversation, read what has happened and choose the next action. Keep staff work close to the customer's question.
- [Conversational intake and forms](https://www.entagl.com/platform/conversational-forms): Collect the information needed for an enquiry without leaving staff to piece it together from unrelated messages.
- [Secure file uploads](https://www.entagl.com/platform/secure-file-uploads): Use a private upload page to collect supported files and connect them to the relevant conversation.
- [Customer CRM](https://www.entagl.com/platform/customer-crm): Keep useful customer details, notes and supported activity in a record your team can work with.
- [Bookings from conversations](https://www.entagl.com/platform/conversational-booking): Help someone move from an enquiry to an appointment request or a supported confirmed booking, according to your setup.
- [Voice AI controls](https://www.entagl.com/platform/voice-ai-controls): Give your calling agent a clear brief. Set the supported actions, choose the voice settings and test the conversation before customers rely on it.

## Plans and availability
[Pricing](https://www.entagl.com/pricing) identifies each product and its tiers, included usage, and additional usage. Do not confuse Comments Automation add-on prices with Receptionist prices. A product's presence in the platform does not mean every product or action is included in every subscription. Channel permissions and individual media/calling capabilities differ.

- [Receptionist plans](https://www.entagl.com/pricing#receptionist)
- [Coordinator plans](https://www.entagl.com/pricing#coordinator)
- [Reputation Manager plans](https://www.entagl.com/pricing#reputation-manager)
- [Studio plans](https://www.entagl.com/pricing#studio)
- [Ads Co-Pilot plans](https://www.entagl.com/pricing#ads-co-pilot)
- [Optional add-ons](https://www.entagl.com/pricing#add-ons)

## Enterprise workflows
### Email support: make room for the cases that need judgment
A routine request arrives in your support mailbox while staff handle a complex case. Configure what the AI may answer, when it should prepare a draft and which requests need a person. Keep work outside that scope out of the automation.

Setup: Mailbox forwarding, sending configuration, approved knowledge, eligible requests and the staff review process.

Pilot measures: First-response time, resolution time, backlog, repeat contact and satisfaction. Agree how a resolved case is counted.

### Website chat: help while the visitor is still there
A visitor reaches a page but cannot find the answer they need. Give them a way to ask, collect the details that help and make the next action clear. Bring staff into the supported workflow when judgment is needed.

Setup: Widget placement, business knowledge, collection fields and escalation. Staff availability must be planned separately.

Pilot measures: Resolved requests, abandonment, qualified enquiries and satisfaction.

### WhatsApp: continue the conversation with context
A customer returns with another question. Your team can review the relevant messages and connected customer details before responding. Define what the AI may handle and what belongs with staff.

Setup: Account connection, platform rules, messaging permissions, available identity information and handover responsibilities.

Pilot measures: Response time, completed requests, repeat contact, handover and satisfaction.

### API and internal systems: start inside an existing application
An employee starts a request in the application they already use. A configured integration passes the conversation to Entagl and receives a response. If another system must change, agree the action, its permitted inputs and the result it must return.

Setup: The source system, authentication, allowed reads and writes, any required human approval, timeouts, retries and exception ownership. Custom connections require engineering and testing.

Pilot measures: Processing time, manual steps, completion, rework and staff effort. These may need measurement in your existing systems.

These are goals to agree during a pilot, not promised improvements. Some measures require data from your service desk, CRM or internal analytics rather than Entagl alone.

An API connects applications. It does not by itself provide on-premise hosting, private model hosting, dedicated infrastructure or unrestricted system access. Standard API access is available under the current Free and Pro terms. Enterprise adds a scoped implementation and operating arrangement.

[Discuss a scoped pilot](https://www.entagl.com/enterprise)

## Industries
[Industries overview](https://www.entagl.com/industries): industry-specific customer-service situations and qualified phone-number options.
- [Retail & ecommerce](https://www.entagl.com/industries/retail-ecommerce): A customer asks whether the right size is in stock. Later they call about delivery. Give your team a way to continue the work with the right store information.
- [Healthcare & clinics](https://www.entagl.com/industries/healthcare-clinics): Someone asks about an appointment while your team is with another patient. A useful first answer should make the next step clear without pretending to give medical advice.
- [Education](https://www.entagl.com/industries/education): A prospective student asks about dates, entry requirements and fees. The answer should come from current program information, with a person ready for exceptions.
- [Professional services](https://www.entagl.com/industries/professional-services): A potential client asks for help, but the first message leaves out the deadline and the kind of work involved. Collect the basics before the right person replies.
- [Automotive](https://www.entagl.com/industries/automotive): A buyer asks about a model while the sales desk is with another customer. A service caller needs an available time. Both need a clear route to the team.
- [Travel & hospitality](https://www.entagl.com/industries/travel-hospitality): A traveler asks about an arrival, then needs to change it. The next answer should use current information and explain when a person must decide.

Shopify and Trendyol are separate current commerce connections. Trendyol listing questions are public Q&A, not private messages. ikas and T-Soft connections are upcoming. Phone-number types, documentation and provider inventory vary by market. Business-initiated WhatsApp calls to the United States, Canada and Egypt are blocked in the current outbound path.

Make (make.com): the Entagl app on Make connects Entagl to other apps without code. New contacts, bookings, orders, messages and calls can start a Make scenario, and Make can create contacts, send messages and book appointments in Entagl. Setup: https://developers.entagl.com/api/docs/make

## Company and evidence
- [Products overview](https://www.entagl.com/products)
- [About Entagl](https://www.entagl.com/about)
- [Newsroom and company facts](https://www.entagl.com/newsroom)
- [Integrations and channels](https://www.entagl.com/integrations)
- [Setup documentation](https://developers.entagl.com/app/docs)
- [Developer API reference (REST API and webhooks)](https://developers.entagl.com/api/docs)
- [Data protection and owner controls](https://www.entagl.com/security)
- [Privacy policy](https://www.entagl.com/privacy-policy)
- [Buyer guides](https://www.entagl.com/blog)
- [Product comparisons](https://www.entagl.com/compare)
- [Book a demo](https://www.entagl.com/contact)

## Developer API reference
Reference for the Entagl Public API: authentication, contacts, conversations, messages, bookings, orders, calls, webhooks and signed event delivery.
- [API reference overview](https://developers.entagl.com/api/docs): authentication, workspaces and permissions, requests and errors, pagination, idempotency and rate limits.
- [Account](https://developers.entagl.com/api/docs/account): Check which user, workspace and permissions a credential resolves to.
- [Contacts](https://developers.entagl.com/api/docs/contacts): Create, find, update, tag, stage and merge the people your business talks to.
- [Tags](https://developers.entagl.com/api/docs/tags): The workspace tag list that contact tags come from.
- [Custom fields](https://developers.entagl.com/api/docs/custom-fields): Contact properties you define, used in custom_fields on contacts.
- [Conversations](https://developers.entagl.com/api/docs/conversations): Open, close, assign and hand over conversations, pause the AI, and leave team comments.
- [Messages](https://developers.entagl.com/api/docs/messages): Send messages and WhatsApp templates as your business, and read message history.
- [Bookings & availability](https://developers.entagl.com/api/docs/bookings): Appointments, free slots and the service catalog. Writes follow the same availability rules as the in-app Calendar.
- [Reminders](https://developers.entagl.com/api/docs/reminders): Team reminders on contacts, conversations and bookings. The workspace owner sees every reminder; anyone else sees the reminders they created or are assigned to.
- [Orders & products](https://developers.entagl.com/api/docs/orders): Orders, their items and timeline, and the product catalog.
- [Calls](https://developers.entagl.com/api/docs/calls): AI phone calls placed by the Coordinator: history, summaries, transcripts and new calls.
- [Campaigns](https://developers.entagl.com/api/docs/campaigns): Broadcast campaigns created in the app: status, results and sending.
- [Users](https://developers.entagl.com/api/docs/users): The workspace owner and team members, for assignments, mentions and reminders.
- [Channels](https://developers.entagl.com/api/docs/channels): The messaging and phone channels connected to the workspace.
- [Closing notes](https://developers.entagl.com/api/docs/closing-notes): The short reasons your team picks when closing a conversation.
- [Webhooks](https://developers.entagl.com/api/docs/webhooks): Subscribe a URL to workspace events. This is what the Make instant triggers call when a scenario is turned on and off.
- [Events](https://developers.entagl.com/api/docs/events): The live catalog of webhook event types, with descriptions and example payloads.
- [API channel (AI chat)](https://developers.entagl.com/api/docs/api-channel): Run your AI agent from your own app or website. Turn the channel on under Channels → API first. These routes take an API key only.
- [Make.com](https://developers.entagl.com/api/docs/make): Entagl has an app on Make, so you can connect Entagl to the other apps you use without writing code. It uses this API with OAuth, so there is no key to copy.

Entagl Inc. Registered mailing address: 1111B S Governors Ave # 48482, Dover, DE 19904, United States. Support: support@entagl.com. Privacy: privacy@entagl.com.

## Capability details
### AI conversation controls
A customer may send several messages, correct a detail or ask for a person. Configure how the AI handles those situations before they happen.

- Let the request arrive: Supported timing controls can group rapid messages before a reply. Choose the behavior that fits the channel and the work.
- Set the boundaries: Define the instructions, response style and rules for handling or ignoring enquiries. Review what the AI may do through its configured actions.
- Keep staff in control: Your team can pause the AI and continue the conversation. Configure handover with the relevant contacts and operating process.

Owner workflow: Review the instructions. Choose reply and handover rules. Test a normal enquiry, an unclear request and a request for a person. Review the conversation and adjust the setup when the behavior needs to change.

Staff can review the conversation and adjust the setup when the behavior needs to change.

Scope: Controls reduce the scope of allowed behavior; they do not guarantee perfect responses. Available controls differ by channel and product.

[Read the full page](https://www.entagl.com/platform/ai-conversation-controls)

### Cross-channel conversations
Customers use different channels. Bring supported conversations and relevant customer information into Entagl so staff can see what they need before replying.

- Connect the channels you use: Start with supported accounts and the permissions each connection needs. Email, website chat and WhatsApp have different setup and messaging rules.
- Review the customer record: Use available contact details and history to understand the request. Identity links depend on the information and confirmation available; a matching name is not proof of the same person.
- Continue with care: Check the relevant conversation and choose the next action. Keep private customer information scoped to the right record and workspace.

Owner workflow: Connect the channels your business uses. Open the customer’s conversation and review their contact record. Confirm the customer’s details when their history is unclear. Continue in the channel where the customer expects a reply.

Staff use the inbox and connected records for the next response.

Scope: Channel connections do not guarantee automatic identity matching or identical features across platforms.

[Read the full page](https://www.entagl.com/platform/cross-channel-conversations)

### Shared team inbox
Open the conversation, read what has happened and choose the next action. Keep staff work close to the customer's question.

- Read before replying: Use the available conversation and translation tools to understand the messages. Review an AI draft before sending it when you need help with wording.
- Leave useful context: Add an internal note and assign the conversation to the appropriate teammate. Keep the reason for the next step clear.
- Do the work in context: Use supported inbox actions for forms, appointments and private uploads. Review the details before completing the action.
- Keep handovers clear: When work needs another teammate, keep the conversation, notes, and assignment together so the next person can continue from the same context.

Owner workflow: Open the conversation and review what has already happened. Use translation tools or an AI draft if they help you understand or reply. Send the reply, pause it, or keep the conversation with the team as needed. Add an internal note, assign the next teammate, or use a supported inbox action.

The assigned teammate can review and continue the conversation.

Scope: Assignment does not guarantee a response time. Available actions depend on permissions and configuration.

[Read the full page](https://www.entagl.com/platform/shared-inbox)

### Conversational intake and forms
Collect the information needed for an enquiry without leaving staff to piece it together from unrelated messages.

- Ask with a purpose: Choose the fields that help your team act. Explain why sensitive information is needed before requesting it.
- Use the right format: Supported forms can appear inside website chat. Hosted form links can be used on other supported channels.
- Review the answers in context: Use submitted information alongside the conversation before making the next decision.

Owner workflow: Create an intake and define questions, conditions, and required details. Choose which answers should be saved to the customer record. Let the AI collect them, or choose Send form from the inbox. Review the submission and the configured next action.

Staff can use the collected information in the relevant workflow.

Scope: A submitted form is not automatically an approved application, order or booking. The next action follows your setup.

[Read the full page](https://www.entagl.com/platform/conversational-forms)

### Secure file uploads
Use a private upload page to collect supported files and connect them to the relevant conversation.

- Make the request clear: Explain which file is needed and what the team will use it for. Send the supported upload link from the conversation.
- Keep the file with the request: Review uploaded material in its customer context, with the relevant access controls.
- Choose how it is handled: Review retention and AI-analysis settings for the workflow. Only enable processing that fits the intended purpose.

Owner workflow: Configure the upload request. Check access and retention. Test the link and the resulting file record. Review the uploaded file in the conversation.

Authorized staff can review the file and continue the work.

Scope: Supported file types, size limits, link access and retention rules apply. Do not use a marketing example as a statement of regulatory compliance.

[Read the full page](https://www.entagl.com/platform/secure-file-uploads)

### Customer CRM
Keep useful customer details, notes and supported activity in a record your team can work with.

- Save what the next person needs: Choose relevant contact fields and review the information collected through conversations.
- See where the work stands: Use supported stages, tags and assignments to organize the next steps. A record should help someone act, not become another place to search.
- Check the identity: Review suggested links and merges through the supported process. Keep different people separate when the evidence is unclear.

Owner workflow: Open Customers and choose List or Board. Select a record and review its stage, tags, and details. Open the profile to review history or update a custom property. Assign the record or move it to the appropriate stage.

Staff can use the available history and details when continuing the relationship.

Scope: Cross-channel identity and record linking depend on evidence and configuration. Customer records do not guarantee automatic attribution of every sale.

[Read the full page](https://www.entagl.com/platform/customer-crm)

### Bookings from conversations
Help someone move from an enquiry to an appointment request or a supported confirmed booking, according to your setup.

- Get the details right: Collect the information your business needs and use the configured availability and booking rules.
- Respect how you confirm appointments: Some workflows require staff approval. Others permit supported bookings directly. Make the difference clear to the customer.
- Let staff finish the work: Your team can review the conversation and use supported appointment actions from the inbox.

Owner workflow: Configure services, availability, and booking permissions. Test a valid request, an unavailable time, and a request that needs staff confirmation. For manual booking, open Create appointment in the inbox and review the details. Check the resulting appointment state in the supported booking workflow.

The resulting appointment state is visible through the supported booking workflow.

Scope: Availability, confirmation and reminder behavior depend on configuration. A demonstration is not a real booking.

[Read the full page](https://www.entagl.com/platform/conversational-booking)

### Voice AI controls
Give your calling agent a clear brief. Set the supported actions, choose the voice settings and test the conversation before customers rely on it.

- Write the brief around the caller: Define the questions, information and next steps the call should cover. Include what happens when the request is unclear.
- Connect only the actions needed: Configure supported tools and test their results. Include an unavailable option and a failed action in the trial.
- Listen to the result: Review the test conversation for accuracy, pacing and a clear ending. The customer should understand what was requested and what still needs confirmation.
- Answer from your website too: Turn on the Call button in the Website channel and visitors talk to the same agent from the chat widget, no number to dial. The call lands in their chat thread with the transcript and recording.
- Setup and review: Select the calling workflow, review instructions and voice settings, then test before enabling it.
- What happens next: Staff can review the available call records and outcomes.

Owner workflow: Select the calling workflow. Review instructions and voice settings. Test before enabling it. Review the available call records and outcomes.

Staff can review the available call records and outcomes.

Scope: Supported voice behavior and actions vary by connection and release. Keep recorded-preview labels until current live availability is verified.

[Read the full page](https://www.entagl.com/platform/voice-ai-controls)