FAQs
Details to help you build with confidence.
Digital Minds, plans and billing, data handling, enterprise rollout, sales, and support.
A Digital Mind is an AI representative built from knowledge, examples, instructions, and boundaries approved by an expert or business. It can answer questions, guide a visitor, collect permitted details, and help move a conversation to the right next step.
It is not the human expert and should not be presented as one. AI responses can be incomplete or inaccurate, so financial, legal, medical, employment, and other consequential decisions still need qualified human review.
A Digital Mind is configured around a specific owner, purpose, approved knowledge, response instructions, and business workflow. It is designed to stay grounded in that context, recognize when it should not answer, and hand off when a person or another process is needed. It is not a general-purpose source of truth.
Supported knowledge can include approved files, text notes, question-and-answer pairs, links, posts, pages, and other sources available in your plan. The plan catalog separates file, Q&A, text-note, total knowledge-source, and daily sync allowances.
Only add material you have the right to use. Keep confidential, regulated, or sensitive personal information out unless your agreement and workspace configuration expressly support that use.
Yes. Workspace owners can shape the introduction, instructions, active knowledge, response boundaries, source behavior, and fallback messages. Teams should test important questions before launch, review conversations after launch, and keep an escalation path for anything the Mind should not decide alone.
Voice replies, a voice model based on your own likeness, and multi-language answers are plan-dependent capabilities. Availability, included voice minutes, provider requirements, consent, and rollout support should be confirmed on the Pricing page or with sales before you depend on them.
Yes. Your team controls which supported knowledge sources are active and can update or remove material as the business changes. Removing a source affects the knowledge available to the Mind, but separate conversation, audience, connector, backup, or legal-retention records may follow different retention rules.
Public self-service rates are still being finalized, so we do not show placeholder prices. The Pricing page shows the plan structure and included capabilities; contact sales for the current cost of the plan or enterprise rollout that fits your workflow.
Self-service plans can offer monthly or annual billing when those options are available in the live catalog. The Pricing page shows the monthly equivalent for an annual option, while checkout shows the amount, currency, billing period, and plan you are confirming. Taxes may apply.
Enterprise work is quoted separately based on the agreed workflow, scale, implementation, governance, integrations, support, and commercial terms.
Allowances include the Digital Minds you can create, knowledge sources, files, video hours, Q&A pairs, text notes, a monthly pool of AI credits, voice minutes, AI store scans, Smart Products, Smart Links, Smart Codes, and messaging channels. Features such as analytics, Smart insights, multi-language answers, theming, and dedicated support also vary by plan. Use the plan comparison for the current limits.
Every AI action spends credits from one monthly pool: a Digital Mind reply costs 4, a Specialist consult adds 4, an agent run costs 4, and training a post costs 2, with videos and files priced by length. Voice is measured in seconds and shown as minutes. Your Plan and Billing area is the place to review the allowance attached to your subscription. If a campaign or rollout may create a short usage spike, contact sales or support before launch.
Yes. You can create an account and begin building a Digital Mind on an available self-service plan. Provider setup, Audience, Automations, connectors, custom limits, or enterprise governance may still require a guided rollout.
You can review current and scheduled plan changes in Plan and Billing. The checkout or applicable order shows renewal timing, fees, and the plan being confirmed. Cancellation remains subject to the paid-plan commitment and terms that apply to your subscription.
Customers retain ownership of their original content. They give Plandora the limited permissions needed to host, process, transmit, and display that content to provide and secure the service. Customers must have the rights and permissions required for everything they upload.
Knowledge you add is processed to operate your Digital Mind and produce grounded responses. The public terms and privacy policy do not make a blanket promise that covers every underlying AI provider, model, or enterprise configuration.
If you need a contractual commitment about model training, data isolation, retention, residency, confidential information, or regulated data, ask sales to confirm the supported configuration and agreement before uploading that material.
Plandora handles account details, Digital Mind knowledge, conversations, audience records, workflow data, and selected connector data as described in the Privacy Policy. Information is retained for as long as reasonably necessary to provide the service, meet contractual commitments, resolve disputes, protect the platform, and comply with law; the period can vary by data type and workspace configuration.
We use administrative, technical, and organizational safeguards designed to protect information. No online service can guarantee absolute security. Enterprise customers can request a review of data residency, private connectors, access controls, and contractual requirements before rollout.
Do not upload confidential, regulated, or sensitive personal information unless your Plandora agreement and workspace configuration expressly support that use. Minimize personal data, remove fields the workflow does not need, restrict workspace access, and confirm the required legal basis, consent, notices, retention, and provider terms before collection.
If the information was collected through a Digital Mind operated by another business, contact that business first because it may control why and how the information is used. Plandora will support the customer in responding where required.
For information controlled by Plandora, email privacy@plandora.com. Identify the account, workspace, Digital Mind, conversation, or record well enough for us to locate it, but do not repeat unnecessary sensitive data in the email. Deletion or restriction may be subject to identity verification and records we must retain for legal, security, billing, or dispute purposes.
Authorized owners and organization members may be able to review conversations and audience records according to their permissions. Visitors should not treat a Digital Mind conversation as private correspondence with the human expert. The deploying business is responsible for appropriate notices, permissions, and lawful use of collected data.
When you enable a connector, selected information may be sent to or received from that third-party service under your direction. That provider has its own terms and privacy practices. Review them, limit the data selected for synchronization, and confirm the connection is suitable before enabling it in production.
Yes. Enterprise is for organizations rolling out governed Digital Minds across teams. The current enterprise scope can include custom knowledge and usage limits, guided implementation, organization ownership, single sign-on, role-based access, private connectors, data-residency review, workflow validation, dedicated support, invoicing, and negotiated commercial terms.
We start with one valuable workflow, identify its knowledge owners and users, map permissions and integrations, define human review and escalation, and agree on a measurable production outcome. The team validates the workflow and provider setup before expanding usage.
Yes. Bring your security, legal, privacy, procurement, integration, residency, identity, support, and volume requirements to sales before uploading sensitive or regulated material. Availability is confirmed for the proposed configuration and recorded in the applicable order or enterprise agreement.
When a visitor shares contact details or takes a configured lead-capture action, Plandora can associate that permitted information with conversation and audience context. Anonymous visitors remain separate until there is a permitted way to identify them. Customers remain responsible for notices, consent, opt-outs, and lawful outreach.
A workflow can start from an approved event, process conversation or document context, apply visible conditions, update an audience record, synchronize a supported connector, or send a configured message. Automations act on the rules, data, and permissions you configure and require testing, monitoring, safeguards, and human review for consequential actions.
The current guided connector rollout centers on Google Sheets, Zoho CRM, and Notion. Audience, Automations, messaging providers, and connectors may require setup and workflow validation. A surface visible in the product should not be treated as production-ready for your account until availability is confirmed.
Use the contact form to describe your Digital Mind, lead qualification, automation, integration, or enterprise goal. You can also email kit.neoh@plandora.com. Include the workflow, expected audience, required connections, timeline, and any security or data requirements so the team can route the request correctly.
Email support@plandora.com for help with an existing account, Digital Mind, billing issue, or product problem. Include your account or workspace, what you were trying to do, the time of the issue, and a safe screenshot or error message. Do not email passwords, API keys, payment-card details, or unnecessary sensitive personal information.
Send privacy and data-rights requests to privacy@plandora.com. Product troubleshooting and billing questions go to support@plandora.com; demos, rates, and enterprise requirements go through the contact form or sales email. This separation helps the right team handle the request.
Build with Plandora