Collections

Different lead types have different shapes. Landlord acquisition needs location, property type, owner, phone; a product order needs customer, address, SKU, COD amount. Collections let you define that shape per lead type instead of forcing everything into one rigid form.

How it works

A collection has:

• Fields — your schema. Each field has a key (used by the API), a label (shown in the UI), a type (text, number, phone, email, select, …), and whether it's required.
• Records — the actual entries. Each record stores its values against your fields, plus a status, an assigned rep, and a source.
• Statuses — the workflow a record moves through (see Velocity & routing).

Creating a collection

1. Go to Collections → New collection.
2. Open it and use the Fields tab to define your schema.
3. Records can now be added in the app, or pushed in from outside via the public API.

Integrate tab

Every collection has an Integrate tab that shows its API endpoint, its field schema, and ready-to-paste curl / fetch snippets — the fastest way to wire a landing-page form to that collection.

Promoting to the pipeline

A record can be promoted into a contact + a pipeline deal, linked back to the original record. This is the bridge from fast capture into a deeper, tracked sale.