Custom CRM Records
Give properties, equipment and projects a record of their own.
Organize the things your business manages alongside the people you serve. Custom records in CreateMomento connect relevant details, relationships and supported workflows.
Built around your work
Make room for the work that matters
One customer may own several properties or pieces of equipment. Storing every detail on the person’s contact record makes it difficult to tell which information belongs to which item.
Custom CRM Records
From a need to a next step
- 01
Define
Choose the record type and useful fields.
- 02
Connect
Link it to the relevant people and records.
- 03
Use
Build a saved view and test the next step.
Where this fits your day
Keep items distinct
Track each property or asset without duplicating its owner.
See the relationship
Understand which contacts and opportunities belong with a record.
Focus a team review
Use a saved list to find records that need attention.
Custom CRM Records
Organize the work around what your business manages.
Start with a repeatable business need. Add structure that helps the team make a decision.
Record types and fieldsKeep the right details together.
Define a record type for a property, asset or project, then choose fields that describe it. A contact remains the person; the custom record holds the item’s details.
Labeled relationshipsShow how the pieces belong together.
Link supported records and label the relationship. Distinguish an owner from a buyer or another involved contact instead of relying on a note to explain the connection.
Saved viewsBring the right work into view.
Save filters, columns and sorting as a saved view. Give the team a repeatable way to review a group of records, with list access checked for the intended users.
Object-based workflowsRespond when a record changes.
Use supported record-created or record-changed triggers to start a configured workflow. Test its conditions and actions before enabling it for everyday work.
Record matchingFind the intended record before updating it.
Supported workflow lookup actions can search by record ID, external ID or field criteria. Define what should happen when there is no match or more than one match.
Related workflow stepsFollow the relationship to the next step.
Supported actions can add or remove associated records from another workflow. Choose the relationship label and test which records are affected.
Custom CRM Records
An example, step by step
A customer with several properties
A property service business keeps an individual record for each location and links it to the relevant contact. Staff can distinguish each address and service status without duplicating the customer.
Illustrative example. Sample workflow, not a live product screen.
Equipment that needs a review
A service team defines an equipment record with an identifier and review status. A saved view brings the selected records together for a staff check. This is a proposed data structure, not an equipment-management system.
Illustrative example. Sample workflow, not a live product screen.
A project status change
A team configures an object-based workflow around a project status field. It tests record matching and the intended next action before using the workflow with real project records.
Illustrative example. Sample workflow, not a live product screen.
Choose the right place for each kind of information.
Custom records extend the CRM. Existing contacts and opportunities still have distinct jobs.
Custom CRM Records
Track a separate type of item with its own fields and relationships.
CRM & Contact Management
Keep people, contact details and customer history organized.
Sales Pipelines
Manage sales opportunities through defined stages.
Integrations & Data Connections
Move selected information between connected tools.
A clear starting point
We check your account, available features and usage needs before recommending a plan. Software access, custom setup and ongoing management are scoped separately.
Questions before you start
When is a custom field enough?
Use a field when the detail belongs to an existing contact or opportunity. Consider a separate record when the same kind of item occurs several times and needs its own details or relationships.
What is the difference between a type and a record?
A type defines the structure, such as Property. A record is one item within it, such as a particular location. Fields describe that item; relationships connect it to other records.
Can we use custom records everywhere in the platform?
No. Support varies by feature. Confirm the intended form, workflow, report or other tool before building around it. Custom records do not automatically inherit all contact features.
Will an identifier prevent every duplicate?
No. Supported unique fields can enforce specific rules, but matching and import design still matter. Review existing data and test how each entry method handles a repeated identifier.
Can a record change start a workflow?
Yes, supported object-based triggers can start configured workflows. Check the available actions and associated-record rules for the process you want to build.
Who can change the record structure?
An authorized administrator manages object definitions. Confirm staff permissions for the actual record tasks and saved views separately; access to a list is not permission to redesign the data model.
Can we delete a type and start again?
Treat object deletion as a permanent change that can remove related records and configuration. Review dependencies and a recovery plan before deleting anything.
Can this replace our industry software?
That requires a separate fit assessment. Record storage alone does not provide every scheduling, inventory, accounting or specialist workflow your business may need.
CreateMomento
Start with the task you want to improve.
Tell us where your team gets stuck. We will help you identify the right tools and a practical first step.
Book a Strategy Call