LOKAL already knows the company
We disclose the relationship before accepting protection. The parties write down whether that prior scope is excluded, paused or makes the account unsuitable.
Partner protection
Moving hotels to Ely removes the obvious direct-service conflict. Written account protection handles the harder question: what LOKAL may do after it learns who your client is.
Decision first
No. Once an account is registered and accepted, LOKAL will not directly solicit or cross-sell competing, extending or bypassing services to that account during the active scope and the agreed protection period, except through the written prior-relationship or independent-inbound process.
Registration
The partner registers the legal company name, known brands and relevant market before LOKAL receives access or joins a meeting. LOKAL checks for a material pre-existing relationship and discloses one before accepting the account.
Commercial ownership
LOKAL performs the services in the statement of work. It does not use delivery access to pitch another LOKAL service, move the client into a direct contract or present its own proposal without the partner’s written consent.
Communication and data
The account record states who may email the client, who joins meetings and which identity is used. Access is kept to the named delivery team. CRM records, credentials and client files are separated by account and are not reused for prospecting.
Publicity
LOKAL does not name the partner, the client or the relationship in a case study, logo strip, award entry, proposal or social post without written permission for that specific use. An anonymised reference must also stay within the agreed boundary.
Exit
On termination, LOKAL stops new work, records open decisions, removes access and returns or transfers the agreed files during the paid transition. The current commercial position keeps account protection and no solicitation in place for 12 months after the last active statement of work unless the signed agreement states another period.
Put it in a real account
We disclose the relationship before accepting protection. The parties write down whether that prior scope is excluded, paused or makes the account unsuitable.
We log the enquiry, tell the partner and do not turn it into an independent sale while protection applies. Any exception needs the written process in the signed agreement.
Permission is specific: client name, numbers, channel, wording, placement and review date. Approval for one deck is not approval for the public website.
Limits matter
Account protection always identifies the registered company. Territory or vertical boundaries are added only when the commercial model genuinely requires them and the signed terms define the edge.
LOKAL discloses a material pre-existing relationship before accepting the account. The parties then document the exception or decide not to proceed.
Only in the communication mode the partner authorises. Direct technical communication can be useful, but it does not change who owns the proposal, price or relationship.
Only with written permission for the exact public use. By default, partner names, client names, logos, results and the existence of the relationship remain private.
LOKAL returns or transfers agreed files, records open decisions, removes delivery access and completes the paid handover. Legally required security, invoice or dispute records may be retained but not used for selling.
Start with one account
We’ll use the brief to put the right operator on the first conversation and flag a mismatch before it reaches your client.