Skip to content
GrandCoders
Documentation

Everything you need before you buy, and after.

Installation, features, licensing, hosting, upgrades, and support. ConverzaFlow buyers use these pages with their Envato purchase code.

PHP / Laravel

ConverzaFlow

Product page
  • ConverzaFlow documentation

    Full product documentation: what ships, install paths, licensing, channels, hosting, upgrades, and how to get support with your Envato purchase code.

    • Start here
    • What you receive
    • Choose your install path
    • Documentation map
  • ConverzaFlow installation

    Illustrated install guide: requirements, folder layout, web installer screenshots, CLI option, cron, mail checks, and first login.

    • Requirements checklist
    • Safer folder layout
    • Choose how you install
    • Step-by-step install
    • After install — smoke test
    • Web-server safety
    • Optional — rebuild frontend assets
  • ConverzaFlow features

    What ships in 1.0 with product screenshots — inbox, channels, workflows, campaigns, CRM, roles, installer, and demo mode.

    • Unified inbox & CRM
    • Official channels only
    • Workflows & campaigns
    • Roles, settings, installer, demo
    • Not included
  • ConverzaFlow licensing

    How purchase codes are verified, stored, and limited to one live installation — with installer context.

    • How verification works
    • Find your purchase code
    • Buyer configuration
    • If verification fails
  • ConverzaFlow on shared hosting

    Document-root layout, Composer-off-host builds, one-minute cron, and the built-in compatibility queue worker.

    • When shared hosting works
    • Safer layout
    • Cron (required)
    • Compatibility worker
    • When Composer/Node are unavailable on the host
  • ConverzaFlow upgrades

    Manual upgrade workflow for 1.0 — there is no in-app updater.

    • Before upgrading
    • Upgrade sequence
    • Rollback
  • ConverzaFlow troubleshooting

    Blank pages, missing assets, database errors, mail and jobs, cron, permissions — with what to send in a support request.

    • 500 error or blank page
    • CSS or JavaScript missing
    • Jobs or mail do not run
    • Scheduled work does not run
    • What to send with support
  • ConverzaFlow channels and credentials

    Official messaging onboarding, Meta callbacks, mail, and the rule that secrets stay in .env.

    • Rules
    • Official messaging
    • Mail
  • ConverzaFlow API, privacy, and backups

    Workspace API scopes, operator privacy checklist, and what a usable backup contains.

    • Workspace API
    • Privacy
    • Backup and restore
  • ConverzaFlow support

    How buyers get help using their Envato licence — what to send, what is covered, and how to contact GrandCoders.

    • Contact with your licence
    • What to include
    • Covered vs not covered

Android

InstantChat

Product page
  • InstantChat documentation

    What ships with InstantChat, the services it depends on, and how to get from download to a running build.

    • What you receive
    • Prerequisites
    • Getting started
    • Configuration
    • Updates
    • Common problems

Android

GrandWeb

Product page
  • GrandWeb documentation

    What ships with GrandWeb, what you need before building, and how its remote configuration model works.

    • What you receive
    • Prerequisites
    • Getting started
    • Configuration
    • Updates
    • Common problems

About this documentation

The pages here cover what you need to know before and around a build: the services each product depends on, what arrives in the download, and where things usually go wrong.

The exact configuration steps for a given release — file paths and key names — ship inside the download itself, and that bundled guide is the authoritative reference for the version you own. Where a step depends on a release, this documentation points you there rather than restating something that may have changed.

If something in a bundled guide is unclear or out of date, that is worth reporting — see Support.

View the CodeCanyon profile