Product Custom properties
Your data model, not ours.
Every business tracks something the software has never heard of — a booking reference, an incoterm, a port, a policy number. Define those as fields and they live on the conversation instead of in somebody’s head.
Why it exists
The spreadsheet nobody keeps up to date
Ask a freight desk where the booking reference lives and the answer is a spreadsheet, a note in a chat, or a colleague. It is never wrong the day it is written; it is wrong three weeks later, because keeping a second system in step with a conversation is work nobody has time for.
Fields defined on the conversation itself remove the second system. The reference sits where the conversation is, it is filled in by the person already reading the thread, and it can be required so it does not get skipped.
What you get
In the product today.
Six field types
Text, date, file, single select, multi select, and dependent — enough to describe most operations without becoming a database project.
Dependent dropdowns
Pick Colombia and the port list narrows to Colombian ports. The child options are defined as a tree against the parent, so agents pick from three options rather than forty-seven.
Required where it matters
Mark a field mandatory and it stops being the one everybody forgets.
Grouped into sections
Organise fields into sections — Shipment, Routing, Billing — so a long panel stays readable.
File fields
Attach the bill of lading or the signed quote to the field itself rather than hunting back through the thread for it.
Ordered how you want
Fields and sections carry an explicit position, so the panel reads in the order your team works in.
When you would use it
Situations this is for
- A freight desk that needs a booking reference on every shipment conversation.
- A clinic recording procedure type and travel dates against each patient.
- A brokerage where the origin country decides which ports are even valid.
Questions
Custom properties — questions
What field types are supported?
Text, date, file, single select, multi select, and dependent. Dependent is the interesting one: the options offered depend on what was chosen in the field above.
Can I make a field mandatory?
Yes. Any field can be marked required.
Is this a CRM?
Custom properties are the part of a CRM that matters when the conversation is the record — your own fields on the contacts and conversations you already have. Pro adds the rest of it: deals with five fixed stages, a value and an expected close date, and a pipeline board. What you still will not find is forecasting, quotas or a workflow builder.
Stop running your best channel off a phone in a drawer.
Connect your first number in five minutes. Keep the number, keep the history, and finally see the whole thing.
No credit card required.