These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Hospitality CRM
- Features
- Organizations and accounts
Organizations and accounts
Keep each hospitality buyer with its operating organization, eligibility context and named relationship.
OverviewAccount directory×
Hospitality CRM · Organizations and accounts
New
Account directory
Accounts
| Name | Code | Contact name | Eligibility note | Organization | |
|---|---|---|---|---|---|
| Account 949 | CDE-106 | Contact 820 | EN-860 | ORG-1233 | |
| Account 853 | CDE-655 | Contact 995 | EN-974 | ORG-3107 | |
| Account 789 | CDE-595 | Contact 149 | EN-745 | ORG-5924 | |
| Account 872 | CDE-571 | Contact 284 | EN-797 | ORG-1172 | |
| Account 237 | CDE-677 | Contact 314 | EN-895 | ORG-1316 |
6 of 6 records
Account 949Accounts · ACC-18363
CodeCDE-106
Contact nameContact 820
Eligibility noteEN-860
OrganizationORG-1233
What you can do
Start with the buyer relationship
An opportunity needs a real buyer and an operating organization before anyone can assess its value. Accounts hold the customer or partner identity, contact name, address and eligibility note. Organizations hold the operating name, time zone and currency. The Relationship Owner uses both when preparing a deal; the App Administrator maintains them so a team does not open the same buyer under different organizations.
For a group seeking a block of rooms, the first question is which buyer is asking and which organization will own the work. An agency and a corporate buyer may both be involved in the conversation, but the opportunity points to one counterparty account. Agree that choice before the owner adds a group stay inquiry.
How the work is organized
- Organization first. The App Administrator maintains the operating organization and its active status, time zone and currency.
- Account eligibility. The account holds the buyer name, code, contact and eligibility note. The team checks it before opening an opportunity.
- One counterparty. The opportunity carries its buyer account and operating organization, making later activity, inquiry and review evidence traceable.
What to agree during setup
Decide how hotel groups, resorts and travel partners map to organizations. Set a code convention that lets a person distinguish similar buyer names. Agree who maintains the contact name and eligibility note on an account, and what review the team expects before a previously inactive account is used again.
The App Administrator should confirm how members belong to an organization. Relationship Owners can then work within the correct operating context; Sales Managers can review work against the same organization. If teams use more than one currency, agree which operating organization owns each opportunity and how the read-only effective exchange rates will be supplied.
Check the handoff on an actual case
Use a corporate travel buyer that requests a group stay at a resort. Create its account with the contact name and eligibility note under the correct organization. Have the Relationship Owner open an opportunity with that account as counterparty, set the expected close date and value, and create a linked inquiry. The Sales Manager should be able to follow the relationship from the opportunity back to its account and organization before making a decision.
Now try an account with a similar name in another organization. The handoff should make the distinction visible through the account code and organization. Check that an Auditor can read the authorized record and its eventual evidence while the App Administrator can still correct the master data.
What your team sees
- Account directory — Active buyer and partner accounts with contact and eligibility context for the next opportunity.
- My open opportunities — The owner’s current deals, with each counterparty visible alongside its status and expected close date.
Follow the work through
Open and qualify an opportunity after the buyer is identified. Review access and ownership before the first operating cycle.
What it keeps track of
Data model- Organizations
- Operating organizations (hotel groups, resorts and travel partners) that own accounts, opportunities and group-stay inquiries.
- Accounts
- Customer and partner accounts (corporate travel buyers, agencies, event planners) eligible for hospitality opportunities.
- Team members
- Internal hospitality sales and review team members with their organization membership and role.
- Users
- Users
- Opportunities
- Hospitality sales opportunities with lifecycle stage, expected value, expected close date and revision guard.
- Exchange rates
- Read-only effective exchange rates for this app.
Who uses it
Permissions- App Administrator
- Maintains Organizations, Accounts and team members.
- Relationship Owner
- Selects the account for Opportunities.
- Sales Manager
- Checks eligibility in review.
- Auditor
- Reads the authorized trail.
Set up Hospitality CRM your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.