Offera/Help/Overview

Offera Help Centre

Understand the main Offera workflows before signing in: workspace setup, AI-assisted request handling, channels, quotes, billing, security, integrations, and common launch questions.

Ctrl K

Help Centre | Offera

Multi-channel quote workflow platform

First workspace setup

Plans, limits, and upgrades

AI parsing, sector packs, and catalogue meaning

Customer requests from connected channels

By topic

Help topics for common Offera workflows

First workspace setup

Start with a workspace, a company profile, the first user, and enough catalogue data to create a real quote without inventing hidden records.

Plans, limits, and upgrades

Offera reads plan names, prices, markets, features, and limits from the governed plan catalogue instead of hardcoding one public table.

AI parsing, sector packs, and catalogue meaning

AI helps turn messy messages into structured draft data, but the catalogue remains the source of truth.

Customer requests from connected channels

Channels let teams receive quote requests from the places customers already use, while keeping ownership and setup state visible.

From customer request to quote decision

A quote keeps line items, totals, PDF status, customer response, and optional signature/payment context connected to the same record.

Subscription, invoice, and refund basics

Billing is intentionally tied to plan catalogue and payment-provider status so public claims do not drift away from the actual plan controls.

Tenant isolation and operational review

Security wording must stay precise: Offera separates tenants, records audit context, and exposes risk signals, but should not claim certifications that are not in the repository or live documentation.

Developer and integration surfaces

Developer-facing features exist, but they should be described as plan-gated and setup-dependent until public API documentation is formally published.

Common launch questions

Troubleshooting should guide the user to the next safe check without pretending the system learned from data or changed catalogue records automatically.

01 / Getting started

First workspace setup

Start with a workspace, a company profile, the first user, and enough catalogue data to create a real quote without inventing hidden records.

How do I open an Offera account?

Registration creates a company workspace and places the user in that tenant. From there, onboarding asks for operating area, locale, and basic company context so the product can show the right setup surfaces.

Sector selection may import suggested attributes and aliases, but it does not create sample products in the catalogue.
Manual attributes and catalogue records remain under the company workspace and are not shared with other tenants.

What is the shortest path to the first quote?

Add or import at least one customer and one product, then create a quote from the dashboard or from an incoming request. The quote can move from draft to sent, viewed, accepted, rejected, expired, PDF, signature, and payment-related states depending on enabled features.

Public quote links expose only the customer-facing response surface.
Internal notes, plan limits, and workspace settings stay inside the authenticated application.

02 / Plans and limits

Plans, limits, and upgrades

Offera reads plan names, prices, markets, features, and limits from the governed plan catalogue instead of hardcoding one public table.

Which plan opens which features?

The live catalogue currently models trial, basic, pro, and pro max style plans. Feature access can include quote volume, product limits, channel limits, API access, audit log, custom domain, e-signature, advanced PDF branding, and accounting automation.

Use the pricing and billing pages as the current source because super admin can publish catalogue changes.
Some markets can be active or inactive independently, so regional display can differ.

What happens when a limit is reached?

The product should show a plan prompt or block the specific action rather than deleting existing work. Existing quotes, products, customers, and channels remain visible according to permissions.

Channel and quote limits are checked against the effective company plan.
Super admin can inspect and adjust plan or limit overrides with an audit reason.

03 / AI backbone

AI parsing, sector packs, and catalogue meaning

AI helps turn messy messages into structured draft data, but the catalogue remains the source of truth.

What does AI parsing actually do?

The parser can use internal tools such as product search, stock checks, price computation, customer context, and final parse submission. A step cap prevents endless loops and failed parses can be routed for human review.

Super admin now surfaces parse failure pressure, manual-review pressure, tool steps, and recent tool-call errors.
If the launch failure rate becomes unacceptable, the model provider can be changed without redesigning the quote workflow.

How should aliases and product fingerprints be used?

Aliases are intentional search hints. Product embeddings can later improve semantic matching, but they must not override business meaning.

Only alias terms that truly mean the same sellable item for that tenant.
If board and lumber, or tahta and kereste, are different products for the customer, keep them separate.

04 / Channels

Customer requests from connected channels

Channels let teams receive quote requests from the places customers already use, while keeping ownership and setup state visible.

Which channels does the product model?

The channel model includes WhatsApp Business, WhatsApp QR, Telegram, inbound email, web form, Instagram DM, Facebook Messenger, Discord, Microsoft Teams, Slack, LINE, SMS, 360dialog, Twilio, and MessageBird.

Plan features decide which channel types can be enabled for a tenant.
Some channels require provider-side webhook or bot setup before they are useful.

How are channel setup and ownership handled?

Channel setup is stored per workspace. Ownership claims, conflicts, releases, and same-device signals are tracked so suspicious channel movement can be reviewed instead of silently accepted.

Super admin security screens explain raw signals such as same-device multi-account events.
Webhook routing is tenant-scoped and tied to the channel record.

05 / Quotes, PDF, and signatures

From customer request to quote decision

A quote keeps line items, totals, PDF status, customer response, and optional signature/payment context connected to the same record.

How does a quote move through the system?

A quote can start as a draft, be sent to a customer, be viewed through a public link, and then be accepted, rejected, revised, expired, signed, or connected to payment and accounting flows depending on setup.

The public response page does not expose the internal workspace.
The audit trail and activity history help explain what changed and when.

How do PDF and e-signature fit in?

PDF generation and e-signature are production-ready workflow surfaces. Offera supports Documenso and DocuSign provider integrations; the active provider is selected by the environment and workspace setup.

Promise the configured e-signature capability, not a specific provider name, until that provider is enabled for the workspace.
Branding and language choices should stay locale-aware.

06 / Billing and refunds

Subscription, invoice, and refund basics

Billing is intentionally tied to plan catalogue and payment-provider status so public claims do not drift away from the actual plan controls.

How are subscriptions managed?

Workspace billing pages show current plan, subscription state, usage, available plans, and payment-provider actions. Paid plans renew until cancelled according to the published terms.

The exact checkout provider can vary by configuration.
If a payment fails, the billing page and provider response should be checked before retrying.

What is the refund policy?

The public refund policy currently states a 14 calendar day refund window for eligible purchases or renewals. Billing requests should include order number and checkout email.

Use the published refund policy as the legal source.
Account-specific billing support should happen through authenticated support when possible.

07 / Security and compliance

Tenant isolation and operational review

How is tenant data separated?

Database records are company-scoped and protected by application permissions and tenant-aware routes. Security and support workflows are designed so one company’s records are not exposed to another company.

Audit logs record important actions and operational context.
Device and channel risk events are review signals, not automatic proof of wrongdoing.

What compliance claims are safe to publish?

Publish only what the live legal pages and verified operational documents support. Do not claim SOC 2, ISO 27001, VERBIS, bug bounty, or a trust centre unless those assets exist and are approved.

Privacy, terms, cookie, and refund pages are present publicly.
Future compliance documents can be linked once they are real and version-controlled.

08 / API and integrations

Developer and integration surfaces

Developer-facing features exist, but they should be described as plan-gated and setup-dependent until public API documentation is formally published.

Is there API access?

The application includes API settings and plan-gated API access. Public FAQ copy should avoid fixed token quotas or endpoint promises unless they match the deployed documentation.

Use the in-app settings page for active token management.
Keep API examples generic until a public OpenAPI document is shipped.

Which integrations are safe to mention?

The product surfaces payment, e-signature, WooCommerce, accounting, and channel-provider integrations. Availability depends on plan, provider credentials, and workspace setup.

QuickBooks and Xero accounting flows are represented in the product copy and provider contracts.
Unsupported local accounting systems should not be listed as live integrations.

09 / Troubleshooting

Common launch questions

Troubleshooting should guide the user to the next safe check without pretending the system learned from data or changed catalogue records automatically.

What if AI matches the wrong product?

Review the parsed request, product catalogue, attribute schema, and aliases. If two terms are different products for the business, do not merge them with an alias just to improve search recall.

Adjust aliases only after confirming business meaning.
Keep uncertain parses in human review instead of sending a risky quote.

What if a channel, PDF, or payment step fails?

Check the workspace setup page, provider status, plan access, and the specific error shown in the UI. Authenticated support should include the page URL, visible error, browser, and approximate time.

For channel issues, verify ownership and webhook setup first.
For PDF or billing issues, attach the quote or order context rather than raw customer data.

Member?

Use authenticated support for account-specific issues

Support inside the product can include account context safely, including URL, visible error, and workspace state.

Open support

Not a member?

Ask before opening a workspace

For launch access or product fit questions, contact Offera Studio without sharing private customer data.

Contact Offera