Search the Jeevi knowledge base, browse FAQs, read feature guides, follow screenshot-led walkthroughs and open the complete handbook. Content can be expanded and customized for each client implementation.
Created by DAIM Hub Fiji · Developed by Sarneet Sahvil Kumar
Browse the selected Jeevi support content.
Customization begins with discovery, not with changing screens at random. We review how the business currently sells, books, confirms, operates, pays suppliers, collects customer payments, communicates and reports.Discovery areasProducts, services...
ViewPayment design is scoped during implementation. The framework can be adapted for deposits, full or partial payment, outstanding balances, pay-later arrangements, bank-transfer confirmation, payment links, manual payment recording and suitable...
ViewJeevi is the core framework, not a rigid one-size-fits-all workflow. We study the client business and tailor branding, fields, statuses, documents, access, payment logic, reports and approved integrations around the...
ViewYes. Jeevi is sold as a core framework. We study the business workflow and then configure or develop the booking process, fields, statuses, branding, documents, roles, reports, currencies, notifications and...
ViewYes. Payment handling is scoped to the business model. Implementations can support agreed combinations of deposits, full or partial payments, pay-later workflows, bank-transfer confirmation, payment links, manual payment status and...
ViewYes. Labels, service names, booking fields, vouchers, invoices, confirmations, email wording and operational documents can be adjusted during implementation to match the client business.
ViewJeevi starts as a core frameworkThe implementation begins by studying how the business receives enquiries, creates reservations, confirms services, works with suppliers, collects payments, operates transfers and tours, communicates with...
ViewPayment design is scoped during implementation because every business has different sales channels, currencies, deposit rules and reconciliation needs.Examples of payment workflowsDeposit at confirmation and balance before service.Full payment at...
ViewThe handbook covers setup, roles, bookings, services, operations, partner records, reports, multilingual use, data tools, vouchers, invoices, communication, customization and support workflows. It contains no passwords or private administrator credentials.
