The Email Factory — mastering review communication
01Communication is part of the review #sec_54c69263
A campaign only produces value if the people concerned know they must act, understand what is expected and can return to the right contact. The invitation, reminder, challenge, decision or end of a campaign are therefore not peripheral messages: they extend the governance process into the inbox.
The Email Factory gives REVIEWIT a common way to prepare and deliver these communications. It brings together what must remain consistent — the business intent, the content, the language, the brand and the authorized sender — while leaving each level of the organization the share of control that is due to it.
This approach avoids two extremes. The business does not have to know the specifics of each mail provider, and the platform does not impose the same text or dispatch identity on all customers and all workspaces.
For a large organization, this separation carries an additional challenge: adopting REVIEWIT must not force it to abandon its domains, its messaging contracts or its responsibility model. The Email Factory makes it possible to keep these assets under its control, and then delegate their use within an explicit framework.
02A business intent before a message #sec_9b60e532
REVIEWIT does not start by asking "what email should be sent?", but "what event must be understood by its recipient?" A review has been opened, a deadline is approaching, a decision requires action or a challenge calls for a response: each of these intentions has governed content and the information necessary for its contextualization.
The message template provides the structure and tone. REVIEWIT then inserts the elements specific to the situation: campaign name, expected role, deadline, resource concerned or other available context. The recipient thus receives a recognizable and useful message, without each component of the product reinventing its own formulation.
This separation is also a protection. Evolving the writing, the language or the visual identity should not require rewriting the operation of a campaign. Conversely, adding a new business event must be explicit: a decorative template that is not linked to any intent does not, by itself, create an operational communication.
03Shared governance, a single chain #sec_886cf54d
The Email Factory distinguishes what belongs to the REVIEWIT foundation, the subscription and the context specific to each workspace.
REVIEWIT maintains the common foundation: the catalog of communications planned by the product, their languages, their publication status and the reference templates. A business intent without content must not remain invisible, and a structural communication must not depend on a local initiative to exist.
The Subscription Manager adapts this foundation to the customer organization. It distributes templates to workspaces, administers domains and authorized senders, and determines how messages will be delivered. This is also where the customer can choose to use a provider operated by REVIEWIT or bring their own.
The Workspace Center places communication in the real context of a campaign. The administrator chooses an available template, a sender and a subject, visualizes the rendering and can exercise the chain by sending a test. It uses a governed capacity without having to administer the technical accounts of the provider.
This delegation prevents a workspace from modifying the transport policy of the entire subscription, while leaving it the necessary latitude to speak to its reviewers with the right context.
04The brand to the inbox #sec_988d61f7
A review message often asks the recipient to follow a link and make a decision. Its credibility depends as much on its content as on its origin. An unexpected sender, an unrecognized domain or inconsistent formatting undermines trust and increases the risk that the message will be ignored or mistaken for a phishing attempt.
The Email Factory therefore links communication to administered domains and senders. The domain is verified with the provider before its normal use; senders can be activated, deactivated and one of them designated as the subscription reference. When a separate reply address is used, it can be confirmed so that replies do not go to a supposed or mistyped box.
Templates, dispatch identity and branding thus form the same trust contract: the recipient must recognize REVIEWIT, understand on whose behalf the message is sent and know where their response will arrive.
05Your domains remain your assets #sec_0f5889f3
An organization can use the domains it already owns in REVIEWIT. It retains its registrar, its DNS hosting and its security rules; REVIEWIT becomes neither the owner of the domain nor the authority over its zone.
The connection is based on proof of control. The Subscription Manager presents the expected records, the organization publishes them in its DNS infrastructure, and the provider confirms that the domain is correctly authenticated. Technical validation and activation in REVIEWIT remain two distinct actions: a domain recognized by the provider is not automatically opened to all uses.
This boundary is particularly important in BYOP mode. Removing a configuration administered by the client from REVIEWIT must not require the deletion of the domain or identity in its provider account. REVIEWIT consumes a controlled authorization; it does not appropriate the asset that makes it possible.
06Choose your provider without changing the business #sec_4be40576
The logic of a review does not depend on a particular mail API. REVIEWIT now knows how to deliver messages via SendGrid, Mailgun, Amazon SES or Scaleway Transactional Email. The choice of provider follows the configuration of the domain and sender; the campaign, however, continues to reason in terms of communication and not transport.
This independence gives the subscription latitude. It can take into account its existing contracts, its localization requirements, its security policy, its volumes or its operational preferences without asking the business to adopt another review process.
It also reduces dependence on a single provider. The transport contract remains common and allows the addition or replacement of an adapter without redefining the catalog of communications. This portability is not, however, an automatic switch: changing providers always requires a valid configuration, control of the domains and publication of the expected DNS records.
07Your delivery infrastructure, under your responsibility #sec_693e6d7d
With the BYOP mode — Bring Your Own Provider, the subscription uses its own transport account with a supported provider. It thus retains the contractual relationship with the provider, its domains, its quotas, its sending reputation, its billing, its operating policies and the rotation of its identifiers.
For a large group, this choice allows it to remain within an already approved, supervised and supported email infrastructure. The deployment of REVIEWIT then introduces neither a parallel provider account nor a sending reputation that escapes existing governance. An organization can favor an actor already referenced by its purchases; another can choose a European provider to support its sovereignty strategy; a third can prefer the service operated by REVIEWIT in order to reduce its administration effort.
In all cases, the sharing of responsibilities remains clear. REVIEWIT governs the intention, the content and the call to transport. The owner of the provider account remains responsible for its availability, its quotas, its reputation, its supervision and the rules that this provider applies to deliverability.
The same principle extends to the private SMTP relay: an organization will be able to connect a gateway that it operates itself, instead of a provider exposing a public API. This option is planned; it must respect the same validation, supervision and life cycle contract before being activable. The choice of transport is expanding, but the level of control does not decrease.
08Delegate usage without delegating control #sec_49cd4f5c
Keeping your infrastructure does not mean concentrating every action in a central team. The Email Factory separates the administration of transport from its daily use.
At the subscription level, authorized managers connect the provider, validate the domains, declare the usable senders and determine those that are active or proposed by default. It is at this level that the decisions that commit the reputation of the domain, the secrets and the relationship with the provider are located.
At the workspace level, administrators use only the capabilities that have been delegated to them. They choose, for a campaign, among the authorized models and senders, adapt the subject and check the rendering by a test. They obtain neither the provider's identifiers, nor the control of the DNS, nor the right to introduce a new delivery infrastructure alone.
This delegation is the point of balance: the central team keeps control of the assets and the risk, while the workspaces retain the necessary autonomy to communicate in their context. Control is not diluted to make usage possible.
09A common catalog, contextualized uses #sec_4e5471b3
The catalog avoids the proliferation of emails written in isolation on each screen. A communication can be prepared once, published in several languages, distributed to a subscription and then made available to the concerned workspaces.
This circulation does not transform the global model into intangible text. A workspace can have variants adapted to its context when governance allows it, while the structural communications of the product retain a common framework. The publication distinguishes what is in preparation from what can really be used.
The preview and test sending complete this governance: they allow to check the rendering, the injected information, the shipping identity and the real path to the provider before applying it to a campaign.
10Prepare, resume, do not send by accident #sec_ee70d9ae
Automatic communications go through a durable queue. The business event is recorded, then a dispatcher resolves the recipient's preferences, the language, the model and the context before entrusting the message to the Email Factory. A temporary error therefore does not force the business to reconstruct the notification from memory.
The operating mode is deliberately explicit. REVIEWIT can keep messages without sending them, simulate their processing or activate real delivery. An absent or unknown configuration remains closed: it must never trigger a real sending by accident.
This chain gives continuity between the business act and its communication. However, it does not transform the Email Factory into absolute proof of reading. The delivery accepted by a provider, the delivery in the recipient's box, the opening of the message and the action in REVIEWIT are four different facts.
11What the Email Factory does not replace #sec_ff625d35
The Email Factory is neither a mailbox, nor a marketing tool, nor a DNS service. It does not create a domain that the organization does not own and cannot guarantee that a provider or a recipient's box will accept each message.
It must not become the only place where an obligation is visible. Tasks, decisions and deadlines remain present in REVIEWIT; the email signals them and leads to them, but does not replace either the business status or the audit trail.
Finally, the freedom of provider does not erase the operational responsibilities. Secrets must be protected, domains maintained, quotas monitored and deliverability feedback exploited. The consolidated tracking of deliveries, rejections and complaints gradually completes this chain; it is necessary not to confuse the requested sending with the demonstrated delivery.
12In summary #sec_b75ac385
The Email Factory transforms email sending into a governed capability of REVIEWIT. A business intention meets published content, a language, an authorized shipping identity and a chosen delivery infrastructure without contaminating the rest of the product with its particularities.
Its power lies less in the number of supported providers than in this separation of responsibilities. The client can keep its domains, its provider account, its reputation and its operating rules; the Subscription Manager gives it control of these assets, then the Workspace Center receives a bounded use of them to contextualize campaigns. The organization can thus delegate transport to REVIEWIT or keep its own infrastructure with BYOP, soon up to the private SMTP relay, without giving up its governance model.