Taly is a SaaS platform that helps organizations manage customer conversations from WhatsApp and social channels, then connect them with customers, team work, orders, bookings, campaigns, automation, and integrations in one place.
Help Center
Clear answers before you start with Taly
Everything teams usually ask about WhatsApp, conversations, orders, bookings, automation, pricing, and support in one place.
Most requested
Questions to start with
All questions
All
Choose a question to view the answer, or use search to get there faster.64 questions
Yes. Taly fits businesses that depend on daily conversations for sales, support, or bookings, especially stores, restaurants, clinics, salons, and service centers.
No. Basic usage is designed for business owners and teams. You can create the account, choose the organization, set up the plan, and connect the channel through clear steps.
The core journey is: create an account, create or choose an organization, activate a subscription, connect WhatsApp, add the team, receive conversations, then use customers, orders, and campaigns as needed.
You can start with the basic setup and enable features according to your plan and business needs. Some paid operating surfaces require an active subscription and the right entitlement.
The organization is your business workspace. It contains users, channels, customers, conversations, orders, subscription data, and permissions.
Yes, depending on the plan and available limits. Branch creation depends on the parent organization's subscription status and branch limits.
Yes. You can add team members and assign roles so each person knows what they can access or manage.
Yes. Taly uses roles and permissions to prevent users from accessing data or settings outside their authority.
The organization can enter a billing pending state. The owner can access subscription and billing routes, while paid operating features remain locked until the subscription is activated.
No. Taly does not replace WhatsApp. It organizes business WhatsApp usage inside a team workspace, with messages connected to customers, orders, and follow-up.
A dedicated business number is usually best. In some cases, an existing number can be used if it fits the official setup, but that depends on the number status and connection method.
Yes. The core integration is built around WhatsApp Cloud API and Meta policies, so some messages, templates, and conversation behavior follow official WhatsApp rules.
Taly supports gradually adding Meta channels inside the inbox according to activation and plans. Campaigns or paid messages for those channels are outside scope unless enabled by a clear product decision.
Yes. The goal is for your team to receive and reply to messages inside Taly instead of depending on scattered devices or personal accounts.
Yes. The team can work from the same workspace, with conversations organized by owner or status so follow-up does not get lost between members.
Yes. Contacts can be organized and connected to conversations, orders, and tickets inside the same organization, while respecting permissions and access limits.
Yes. A conversation can be linked to an owner or follow-up status so the team knows who is handling the customer and what next step is needed.
Yes. Tickets help organize issues or requests that need clear follow-up until they are resolved, instead of leaving them as scattered messages.
Yes. The team can use internal notes or states according to the available operating surfaces, without sending those notes to the customer.
Yes. You can create campaigns for customer groups or segments according to the plan and the policies available for each channel.
No. Campaigns are subject to plan limits, subscription status, channel readiness, and WhatsApp or Meta policies.
For messages outside the conversation window or depending on message type, you may need Meta-approved templates before sending.
Yes. The system works with sending logs, scheduling, and retry attempts according to each message status, so campaign results are easier to follow.
You should not. Campaigns should be used responsibly, with customer consent and channel policies respected, so the business number and customer experience are protected.
Yes. Automation can answer repeated questions, guide the customer, or perform simple steps, while employees can still take over when needed.
Not necessarily. Flow Builder v2 access depends on the organization's plan and entitlement, and it will not run if the feature is unavailable.
No. Automation helps the team and reduces repetition, but it does not replace human judgment in sensitive or complex cases.
Yes. The system is designed to move from an automated flow to human follow-up when needed, so the customer does not get stuck in the wrong path.
Yes. Flow Builder validates graph shape, nodes, and states so an invalid or unsafe flow cannot be published.
Yes. AI can help with replies, summaries, classification, or suggested next steps for the team depending on enabled features.
Not necessarily. AI can be used as a team assistant, and replies may need human review depending on business settings and conversation type.
The privacy policy explains that customer data is not used to train general public models, and processing is performed to provide the service when the feature is enabled.
They should not be used alone for legal, medical, financial, or sensitive decisions. AI is an assistant, and the final decision belongs to the team.
AI feature access depends on available settings and plans, and usage can be organized according to the organization's policy and team needs.
Yes. One of Taly's core goals is to turn commercial conversations into clear orders that can be tracked from creation to payment and fulfillment.
Yes. The system supports a product and category catalog, with plan limits and features such as import or export when available.
Yes. Restaurant-specific capabilities include menus, sections, modifiers, and order preparation depending on features enabled in the plan.
No. A payment proof alone does not confirm payment. Payment is confirmed after trusted review or a payment gateway callback according to the payment method.
Yes. Customer checkout, action, and receipt links can be created while keeping internal metadata and tokens hidden.
Yes. Taly can organize services, appointments, customers, resources, and reminders depending on business type and plan.
The booking journey can be organized from the conversation into a clear appointment inside the system, according to service setup, availability, and plan.
Yes. The bookings system supports resources and availability when Commerce Bookings is enabled, so appointments match real capacity.
The system supports booking deposit foundations depending on activation and payment method, with a clear separation between payment proof and final confirmation.
Bookings work when Commerce Bookings is available for the plan or organization. Without it, normal store or product workflows remain separate.
Yes. Plans differ by usage, number of users, limits, channels, campaigns, automation, commerce, and bookings.
Yes. You can start with a suitable plan, then upgrade as your team grows, message volume increases, or you need additional features.
No. The plan price covers Taly platform usage. Official Meta and WhatsApp fees are separate and depend on message type, country, and usage.
No. A manual payment proof does not activate the subscription before admin approval or trusted confirmation, to keep billing safe.
Yes. Billing, subscriptions, invoices, and payments are linked to the organization context, with amount, currency, and processor checks before financial effects are activated.
Yes. Developer APIs are available for use cases such as contacts, messages, campaigns, and some commerce operations according to documentation and permissions.
Yes. Any resource accessed through the API must belong to the same organization, otherwise the system returns a safe error instead of exposing another organization's data.
Yes. API rate limits and plan-related limits protect system stability and prevent unsafe usage.
Yes. Events can be sent to external systems when Developer Webhooks are enabled and the organization is subscribed to the required events.
Yes. Webhooks use signing, delivery attempts, and header policies. Commerce events are sent only when the add-on is available and the event is subscribed.
Yes. The system is built around multi-tenant boundaries so one organization cannot read or modify another organization's data.
Yes. Roles and permissions control who can reply, manage settings, administer the workspace, or access data.
The system supports security mechanisms such as verification, permission limits, and protected sensitive routes according to user type and settings.
Contact support at support@talyapp.net using the same email linked to your account, and explain that the request is related to data deletion.
Yes. Orders can move through statuses such as new, preparing, ready, out for delivery, completed, or canceled depending on the business workflow.
Yes. Reminders are an important part of the booking experience because they reduce missed appointments and improve commitment, especially for time-based services.
The right plan depends on user count, message volume, campaigns, automation, orders, bookings, and whether you need additional channels.
Customer data is handled seriously and clearly, with team permissions based on each user's role so business owners know who can access or manage information.
Contact the Taly team through the contact page or support@talyapp.net, and we will route your request to sales, support, account help, or technical setup.
Need a more specific answer?