Loading...
Documentation
A practical map of the OnloZap workspace.
Use this page as the public entry point for the product areas you will configure first: workspace setup, sales records, agreements, delivery, invoicing, portal access, and Zapling.
Workspace setup
Start by setting company identity, user access, email sending, payment settings, and portal appearance.
- Invite users and assign access intentionally.
- Connect billing and email settings before sending client-facing artifacts.
Clients and quotes
Create client records, draft quote details, send quote links, and track the commercial response.
- Keep client contacts and workspace ownership accurate.
- Convert accepted quotes into projects or invoices when the work moves forward.
OnloSign documents
Prepare agreements, use templates, manage signers, and keep evidence connected to the client.
- Review generated document content before sending.
- Track signer state and consent from the document record.
Project delivery
Use projects, tasks, issues, schedules, milestones, time tracking, and team workload views.
- Keep project status aligned with what the client sees.
- Use tasks and issues to separate planned delivery from blockers.
Invoices and payments
Create invoices, send payment links, monitor status, and keep revenue tied to the client record.
- Configure Stripe before expecting checkout to work.
- Use invoice status and reminders to reduce manual follow-up.
Portal and conversations
Give clients access to eligible quotes, invoices, projects, files, documents, and messages.
- Portal users are not workspace users.
- Use portal-specific access rules for client-facing records.
AI guidance
Zapling documentation should be read with governance in mind.
Zapling is useful because it reads workspace context. That also means teams should understand permissions, approval steps, credits, moderation, and review expectations.
Chat and summaries
Use Zapling to summarize client and project context, draft replies, and prepare handoffs.
Recommended actions
Review proposed workspace changes before executing them, especially for client-facing or billing work.
Workspace-only boundary
Zapling belongs to authenticated workspace operations. Client portal users should not receive internal AI controls.
Escalation path
If a guide is missing or something behaves differently from the docs, send the route and reproduction steps to support.
Next step
Looking for a step-by-step walkthrough?
The workflow page explains the lead-to-paid lifecycle, while support can help with account-specific setup questions.