For client intake and communication

The request is in. Get the work moving.

Find what is missing, prepare the next reply and make the handover clear. CompanyOS helps your team turn an incoming message into a useful next step.

Discuss your intake process See a request move forward

Your team reviews the reply. The next action stays visible.

Jordan Taylor

Email · Shared inbox · today 09:12

Awaiting information

Example data

Client request

Could you review the scope using the document I mentioned in my previous message?

Referenced document

Scope document from the previous message

Not attached

Information needed

The document mentioned in the previous message is not attached.

Draft for review

Hi Jordan, we do not have the document mentioned in your message. Could you send it so the team can review the scope?

Not assumed · The draft does not describe the document’s contents or confirm the scope.

Next step

Check the document when supplied, then assign the scope review.

Responsible person · Sam Ellis · Coordinator

Saved

Product specimen · Example data

A message is not always enough to start.

A document is missing. The scope is unclear. Nobody knows who should ask. Bring the open question beside the request, instead of leaving it somewhere in the thread.

The same request, before and after preparation.

Request received

New request

The message refers to a document that is not here.

The scope cannot be reviewed yet.

Nobody is named to ask for it.

Ready for the next step

Awaiting information

The missing document is named beside the request.

A precise question is prepared for your team to review.

The scope review has a responsible person. The request still awaits the document.

Ask the question that moves things forward.

Prepare a reply from the available information. Missing details remain visible, so your team can ask for them rather than guess.

Source · New client request

The referenced document is absent. The request is awaiting clarification.

Information needed

The document mentioned in the previous message is not attached.

Draft for review

Hi Jordan, we do not have the document mentioned in your message. Could you send it so the team can review the scope?

Not assumed · The draft does not describe the document’s contents or confirm the scope.

Film · The missing piece

The missing piece

Storyboard and narration, beat by beat.

Film poster: a new client request where a referenced document is missing. A draft for review asks the client to send it; it is saved, awaiting information, with the next step to check the document and assign the scope review. Example data.

Narrated animatic · not the final film

The video is not published yet. The transcript covers everything it shows.

Read the transcript

The request is in.

The request has arrived. But the work cannot start yet.

What is missing?

One document is missing. One question is still open.

A useful next reply.

CompanyOS brings the available information beside the request and prepares the next question.

Reviewed by your team.

Your team checks the wording and the source before anything goes further.

A clear handover.

A named next step replaces the unclear handover. The missing information stays visible.

Get the work moving.

CompanyOS. Turn incoming requests into work your team can move forward.

Hand over the work, not the confusion.

Keep the source, prepared response and responsible person together. A request waiting for information is shown as waiting, not magically complete.

New client request

Jordan Taylor

Awaiting information

Source

The referenced document is absent. The request is awaiting clarification.

View source

Draft for review

Hi Jordan, we do not have the document mentioned in your message. Could you send it so the team can review the scope?

Next step

Check the document when supplied, then assign the scope review.

Responsible person · Sam Ellis · Coordinator

Saved

Example data

Written walkthrough · Example data

One request, from arrival to a clear handover

From request to next step.

A request has arrived, but there is not enough information to start. Let’s prepare the right question and make it clear who takes the next step.

Read what arrived.

Open the message and its documents. The client refers to an attachment that is not here.

Prepare the right question.

The assistant prepares a reply asking for that document. The question is specific to this request.

Review with the source.

Read the source and adjust the wording. The person handling the request stays in control of the reply.

A clear owner. An honest status.

Save the next action with its responsible person. When we reopen the record, the handover is clear and the request still awaits the document.

Discuss your intake process.

That is the work between receiving a request and being ready to act. We configure CompanyOS around your recurring requests, existing tools and data requirements.

Your form captures it. Your team still has to act.

CompanyOS helps with the preparation between receiving a request and taking the next step. We confirm how that fits around the inbox, form or CRM you already use.

Stays where it is

Requests keep arriving in your inbox or form.

Your CRM remains the record you already use.

Your team sends replies the way it does today.

What CompanyOS adds around it

Brings the request and its available sources together.

Names what is missing and prepares a question for review.

Saves the next action with a responsible person.

The data boundary

Each person works with the information they are allowed to use.

Connections are configured explicitly with your team.

Customer-hosted installation and local AI processing are available as explicit choices.

Set up around your process.

Agree one recurring request type, the information needed and the people involved. We configure the supported connections, access and processing boundary with your team.

Questions intake teams ask

We already have a CRM. Does this replace it?

Not by default. We look at the work that still happens around it, such as checking context and preparing a response, and agree a supported fit.

What happens when information is missing?

The example shows a precise clarification prepared for review. Missing information must not be presented as known, and the request stays in its actual state.

Can it work with confidential documents?

The setup must match your access and processing requirements. Customer-hosted installation and local AI are available as explicit choices within the agreed scope, not a blanket promise about every connection.

Where does a new request usually get stuck?

Bring one example with personal details removed. Let us look at the missing information and the handover.

Discuss your intake process

Questions intake teams ask

We already have a CRM. Does this replace it?

Not by default. We look at the work that still happens around it, such as checking context and preparing a response, and agree a supported fit.

What happens when information is missing?

The example shows a precise clarification prepared for review. Missing information must not be presented as known, and the request stays in its actual state.

Can it work with confidential documents?