USE CASE · CONNECTIONS WITH CONTEXT

A recommendation.
A reason someone can understand.

Bring local places together while keeping network membership, editorial recommendations and disclosures distinct.

Illustrative cultural shop representing a local partner recommendation
Illustrative place and photography. No customer affiliation.
See reviewed publication in the productActual LocatorStudio guided publishing showing local, saved and live revisions with fictional project dataOpen capture

Save the shared draft, inspect the customer view and publish explicitly. A save alone does not publish. Actual product · Fictional project data.

What this setup includes

  • Participating-place relationships
  • Recommendation reasons and disclosures
  • Reviewed customer content
Example networks
  • Merchant communities
  • Tourism guides
  • Hospitality partners
  • Member organizations
AN ILLUSTRATIVE CUSTOMER QUESTION

“Why is this bookshop pointing me to that café?”

An explicit recommendation can state the reason and disclose the relationship. That edge is different from both businesses appearing in the same directory. The destination still needs useful hours, photographs and contact details of its own.

Information behind the answer

Membership
Participation in a defined network
Recommendation
An approved directed connection between places
Context
Reason, disclosure and applicable expiry
CUSTOMERS & THE TEAM

Who uses this setup.

Partnership coordinators

Review network participation and the relationships that can be published.

Local editors

Explain a recommendation and provide appropriate disclosures.

Visitors exploring an area

Understand the connection and inspect the recommended destination.

Separate the types of relationship.

A brand carrying relationship answers where a product belongs. Network membership identifies participants. A recommendation describes a reviewed direction from one place to another. Keeping those meanings separate makes the directory easier to maintain and explain.

  • Review participation independently from recommendations.
  • Keep material relationships and reasons visible where applicable.
  • Do not imply endorsement through a shared category or map alone.

Give visitors a useful next step.

Pair the relationship with a readable place detail and an appropriate action. Editorial collections can introduce a theme, while individual recommendations explain the connection. Check current permissions and eligible content before releasing the directory.

  • Inspect the recommended place and its contact destination.
  • Review withdrawals, expiry and changed relationship details.
  • Treat ratings, marketplace transactions and optimized itineraries as separate requirements.
SET UP WITH PURPOSE

Your starting plan.

  1. Define the network

    Agree participation criteria and who is responsible for the directory.

  2. Review connections

    Approve the specific relationships, reasons and disclosures to publish.

  3. Follow the recommendation

    Read it as a visitor and verify the resulting place details and next action.

SETUP QUESTIONS

Before you begin.

Is directory membership an endorsement?

No. Membership and independently approved recommendations are distinct in the product model.

Can relationships expire or be withdrawn?

The app includes reviewed relationship workflows and expiry/withdrawal states. Verify the chosen customer release and current access rules during setup.

Can a guide include products and stories?

Eligible place, product and media content can support editorial discovery. Permissions, rights and public visibility still determine what can be released.

MAKE YOURSELF EASY TO FIND

Plan your locator.

Bring your locations and the customer task you need to support.

Plan your locator