Disambiguate Templates Before You Draft

Three plausible meanings, three decisions

Intent one is a service inquiry from a potential client to a consultancy. Its job is to learn scope, process, conflicts, and disclosure practice—not to request assured publication. Complete draft: "Subject: Question about your Wikipedia-related consultancy process. Hello Nora Ellis, I am Maya Ortiz, procurement lead at Harborline Logistics. I am assessing support for correcting and sourcing information about Harborline’s public company page. Could you explain Northline Editorial Advisors’ scope, how you handle Wikipedia’s conflict-of-interest guideline and paid-contribution disclosure, which work you perform through talk-page requests or Articles for Creation, and what you cannot promise? I am not asking for assured placement. If this is outside your scope, a brief no is helpful. Regards, Maya Ortiz, Harborline Logistics, 18 Dock Street, Portland, ME 04101." The draft names the task without presuming authority. A procurement lead may object, “We only need a page fixed; why ask about process?” Because the process determines whether the proposed work respects disclosure and independent review. Ask the consultancy to identify the employer and client relationship, the accounts that would contribute, the route for requested edits, and the evidence it needs. Ask what happens when independent editors disagree. Can the firm explain limits without falling back on secrecy or assured outcomes? If not, the buyer has learned something important before any engagement. The email's purpose is not to negotiate a favorable article; it is to test whether the provider can describe an accountable, policy-bounded service.

Verify the inquiry before sending. Identify the consultancy from its own site, check that the recipient handles the service, and describe the article or issue without implying ownership. Ask how the firm documents sources and negative or disputed material. A serious answer should distinguish paid advice from community editorial decisions. Wikipedia says no one controls an article, and requested edits remain subject to the same standards as other content; editors may decline them.

Success for this first intent is a clear, relevant explanation of process and limits. A fast promise of assured creation, permanence, deletion, or positive coverage is not success; it is a reason to investigate. Preserve the consultancy's stated employer/client disclosure route and proposed editing process in the procurement record.

Do not convert a service inquiry into disguised instructions to edit an article directly. If the organization has a conflict, the safer operational question is how proposed changes will be disclosed and reviewed by independent editors—not how quickly the firm can make the page say what the client wants.

Use a purpose-specific message structure

The researcher should anchor policy statements to Wikipedia's own pages. The COI guideline describes the situation created by clients, employers, financial relationships, family, friends, and other external relationships; it strongly discourages direct editing of affected articles. The paid-contribution policy requires disclosure for compensated contributions. A consultancy interview can explain practice, but it cannot relax those rules or establish that a proposed change will be accepted.

Keep research and outreach records separate. Record the policy version checked, the interviewee's role, what may be quoted, and which statement is opinion rather than policy. Remove the word "Wikipedia" from the draft as a stress test: if the remaining message still claims encyclopedia endorsement or editorial authority, the framing is misleading. OKKI Go may help retain B2B account context and route a draft for review after the research task is clear; it cannot interpret Wikipedia policy or validate a consultant's authority.

Success for research is an auditable source rationale and a transparent account of limits. Do not merge response rate, service sales, and policy accuracy into one metric. A respondent can be commercially interested while supplying weak evidence; a nonresponse says nothing about the policy itself.

Publicly visible does not mean decision-relevant

Public visibility is not enough to make a fact decision-relevant. Preserve the page, revision or publication date, exact text, and the inference you intend to make. Do not tell an organization that it "needs" Wikipedia work merely because a page exists or contains criticism. Wikipedia's neutrality and reliable-source standards are not sales triggers. The email should describe the observed issue narrowly and give the recipient room to reject the sender's interpretation.

Disclosure is not a footer added after persuasion. A paid contributor must disclose the employer, client, and affiliation for compensated contributions. On English Wikipedia, paid editors are also expected to follow the COI guideline, are strongly discouraged from editing affected articles directly, and may propose changes for independent review. The policy does not promise that another editor will accept the request. Put those limits in the commercial explanation before a buyer relies on the service. The buyer objects, “Disclosure should be the consultant's problem after we hire them.” It is already a procurement issue because the proposed method determines reputational and editorial risk. Ask where the employer, client, and affiliation will be disclosed; which user accounts would contribute; whether requested edits will be placed on an affected talk page; and how the firm will handle a decline. Can you inspect the cited independent sources before approving the engagement? Can the consultant show a route that does not depend on direct conflicted editing? If the answer is vague, pause. A contract cannot turn an undisclosed or promotional process into neutral encyclopedia work, and payment cannot buy acceptance from volunteer editors.

Success for disclosed outreach is a qualified conversation in which the recipient understands the sender's identity, commercial purpose, policy boundaries, and lack of editorial control. A reply asking for assured placement is not a qualified progression until that expectation is corrected in writing.

Transparency is part of the offer

Before using any template, write an interpretation label at the top: service inquiry, research inquiry, or disclosed consultancy outreach. Add recipient class, purpose, policy source, commercial relationship, allowed inference, and stop condition. A reviewer should be able to reject the draft without guessing which task it serves.

If compensation could follow, do not wait until editing begins to discuss disclosure. Ask who the employer and client will be, where disclosure will appear, which accounts are involved, and whether proposed changes will be submitted for independent review. Keep a visible list of paid contributions where the applicable policy requires it. These are operating questions, not copy flourishes.

A clean template makes refusal easy. The recipient can say the service is irrelevant, the researcher can decline to share material, and the organization can request no further contact. The consultant must also be able to refuse a client demand that would require concealment, misrepresentation, or assured editorial control.

Define success after disambiguation

Use the official policy pages as the boundary record. Capture the URL and check date, then note that community guidance can change and that different Wikimedia projects may have additional rules. This article describes the cited English Wikipedia and Wikimedia disclosure framework; it is not legal advice and does not replace review for a specific project or jurisdiction.

OKKI Go can support a reviewed B2B drafting flow after the consultancy task and recipient are clarified. Keep the policy evidence, sender identity, and forbidden claims locked during drafting. A generated message cannot decide whether an editor has a conflict, whether a source is reliable, or whether a community will accept a proposed change.

The final test is simple: can a reader identify which of the three intents the email serves, who pays whom, which public fact is being used, what the sender cannot promise, and how the recipient can decline? If any answer is missing, do not send. Ambiguity here is not flexibility; it conceals the relationship the policy requires the parties to expose.