Your team needs to know which service a client bought, when a renewal is due, and whether a prospect is a fit. If those details live in whichever note someone happened to write, finding them becomes its own task.
Ariyel custom fields give recurring information a consistent place on contacts, deals, and tasks. The useful starting point is the information your team needs to act on.
A field should earn its place by helping someone make a decision, find a record, or complete work with less uncertainty.
Start with the decisions
Imagine your business offers two services. The sales team needs to record the service being discussed, delivery needs to know what was purchased, and the account manager needs the renewal date.
A service-type field on the deal gives the opportunity a clear category. A renewal-date field gives the team a date it can review. A qualification-status field can record whether the prospect meets your agreed criteria.
Keep longer explanations in notes. A field is useful for information you want to filter or compare; a note is useful for the context behind the value.
This makes the process behind your CRM more explicit. The team can agree on what a value means instead of interpreting a different phrase on every record.
Choose the right type
Use Single select when one choice should apply, such as the service sold on a particular deal. Use Multiple select when several options can apply together.
A Date field fits a renewal date. A Person field fits a workspace member responsible for a particular part of the relationship. Text fields hold shorter or longer written information, and a URL field gives a useful link its own place.
Choose option names people can distinguish. “Needs review” and “Qualified” describe different states. Similar labels with unclear boundaries encourage inconsistent data.
Add the field where it belongs
An owner or admin can open Settings → Objects, select the relevant object, and choose Fields → New field. Pick the type, write a clear name, and add a description if the field needs guidance.
Put customer-level information on the contact and opportunity-specific information on the deal. A single customer may have several opportunities, so the service attached to one deal should not automatically describe every engagement with that customer.
Use View settings to show the new field in the relevant table or deal cards. Field order on records and visible columns are separate choices, so review both surfaces.
Make the information useful
Once the team uses a field consistently, it becomes easier to find the records that need attention. You could filter deals to one service type or find records where a qualification field is empty.
Save a recurring question as an Ariyel view. When a contact's information also needs to appear on a deal, consider a Lookup field so you can display the source value through the relationship.
Start with a small set and review actual records together. If people keep leaving a field blank, find out whether the information is unavailable, the instruction is unclear, or the field is unnecessary.
Keep the model manageable
There are 50 fields per object, including built-in fields. Field types can become locked when records contain values or dependent lookups use them. Choose the type carefully before your team starts filling it in.
Deleting an ordinary field permanently removes its stored values. Hide an unneeded column when the goal is simply a cleaner view, and review dependencies before removing a field.
A useful field structure grows with the work. Follow the Custom fields documentation to configure your first additions and understand the available types and limits.