We are planning to use Hubspot to interact with our customers.
However, we have encountered some issues:
1. We have two types of customers - those who purchase our product and partners who will have the ability to resell the product. We want to separate these customers so that they are in different tables. But in Hubspot we found only one section - Contacts. What is the best way to separate our customers? An important point: we need to be able to read and modify each of these sections through the API.
2. Do we understand correctly that there is a limit of 10,000 contacts and we can't have more? Maybe we misread the documentation and there is just a limit of 10,000 entries on a search request or something?
3. Is it possible for the Client to create a property with a link (e.g. to a document stored on external resources) and set up a template for emails so that we can send emails that contain that link? We also should have an ability to create clients and fill this property in via API.
1. There are a few options. Yes, they would all be contacts in HubSpot and it's a matter of labeling them to tell them apart. You could create a custom property with selection options (Properties API endpoint). This is the easiest option. Alternatively, you can use the new association labels (Associations API endpoint). These let you label the relationship between a contact and a company. Lastly, if resellers are an entirely different breed, it can make sense to evaluate whether they should be their own custom object. They could then be associated with companies and contacts.
1. There are a few options. Yes, they would all be contacts in HubSpot and it's a matter of labeling them to tell them apart. You could create a custom property with selection options (Properties API endpoint). This is the easiest option. Alternatively, you can use the new association labels (Associations API endpoint). These let you label the relationship between a contact and a company. Lastly, if resellers are an entirely different breed, it can make sense to evaluate whether they should be their own custom object. They could then be associated with companies and contacts.