iAmBruno.
Your illustrated manual · 13 practical chapters

Concierge

Email the idea. Review the proposal. Keep the conversation going.

Concierge takes requests in email and replies in the same conversation. We will ask for one website-section change, check the designer’s proposal, approve it, inspect the result and request one small revision. The dashboard lets you follow the history; it is not a live voice or chat-app composer.

Download the PDF ↓Open Concierge ↗

Before you start

  • Concierge must be active. Use your registered email and connected tools with available permissions and credits. This is the current email channel, not a marketing app prototype.
  • For a website request, give the facts and desired change. Bruno prepares the designer’s proposal; approve only the work you want applied.
  • For images, describe the image or edit and orientation; optional references can be JPG, PNG or WebP photos. Email intake does not read PDFs: put essential document facts in the message. With Image Maker active, Bruno makes one image/edit per request using your credits, saves it in Image Maker and attaches it to the reply.

Actual Dashboard 2.0 templates, original settings JavaScript and the actual branded Concierge email renderer are used. All history, addresses and website outputs are fictional illustrative fixtures. No mailbox was opened, no email was sent and no website was changed. Marketing app prototypes are not live app features.

01

Find the current Concierge workspace

Find the current Concierge workspace — actual Bruno interface with fictional example data
Atelier Demo · Example account and simulated responses. Open the picture to zoom.
  1. 1The current access and email-first service.
  2. 2Open a new email addressed to Concierge.
  3. 3Ticket list and optional history-sharing control.
  4. 4Read saved messages and responses here.
  1. Choose Concierge in the main dashboard menu. Check the active or pilot label first.
  2. The email link starts a request in your mail app. Your requests lists saved tickets; Your recent conversation shows their messages and responses.
  3. The optional WordPress-sharing box is separate from sending a request. Leave it off unless you intentionally want to share this context with your own connected WordPress chat.
What happens nextYou know where to send work, where to follow it and which setting is optional.
02

Send a clear request from the registered address

Send a clear request from the registered address — actual Bruno interface with fictional example data
Atelier Demo · Example account and simulated responses. Open the picture to zoom.
  1. 1The recipient link opens your own mail app.
  2. 2The account-address, reply-thread and service-access requirements.
  1. Write from your registered address to concierge@iambruno.com. A new email starts a ticket; Reply continues the same request. The dashboard link opens your own mail app.
  2. Our example asks for Friday Coffee on 23 October, 9–10:30 AM, in the orange welcome section. It identifies the connected site, keeps images and other pages intact, and asks for a proposal before publishing.
  3. The first request is acknowledged. Normal follow-up replies wait for an answer rather than another routine receipt. If confirmation is requested, use its private four-day link; do not resend the request.
What happens nextConcierge can ask for missing facts or return a specific proposal in the same email conversation.
03

Read what the designer actually proposes

Read what the designer actually proposes — actual Bruno interface with fictional example data
Atelier Demo · Example account and simulated responses. Open the picture to zoom.
  1. 1Expand the saved message.
  2. 2Your original facts and preservation request.
  3. 3The designer’s specific proposal and approval question.
  1. Expand the saved conversation in the dashboard. The example shows your request followed by “The designer proposes…” and a specific headline, time and button.
  2. Check the scope as carefully as the new design: orange and black remain; images, navigation, logo and other pages stay intact.
  3. The approval question is still a question. If anything is wrong, reply with the correction instead of approving. A proposal is not proof that the website has changed.
What happens nextYou can approve a clear proposal or ask for another direction before the requested publication.
04

Review the proposal in your inbox

Review the proposal in your inbox — actual Bruno interface with fictional example data
Atelier Demo · Example account and simulated responses. Open the picture to zoom.
    1. This is Bruno’s actual branded email renderer, filled with our fictional proposal. Your mail app supplies its own Reply control around the message.
    2. Read the specific art direction, what stays intact and the final “Shall I have them go ahead…” question.
    3. If happy, use Reply and clearly approve this proposal. Otherwise explain what to change. Keep your reply in this thread instead of sending a new unrelated email.
    What happens nextYour reply continues the existing request, with the proposal available as context.
    05

    If a reply says work is in progress

    If a reply says work is in progress — actual Bruno interface with fictional example data
    Atelier Demo · Example account and simulated responses. Open the picture to zoom.
    1. 1The new message in the same conversation history.
    2. 2The explicit approval tied to this proposal.
    3. 3An illustrative working status, not a delivery guarantee.
    1. Reply with clear approval of the specific proposal. Our example approves the welcome section while preserving every other page and image.
    2. If a reply says the designer is working, it is not a delivery. This screenshot illustrates a possible status message, not a promised extra email after every approval.
    3. You do not need to send a status request to make a saved task finish. Follow the actual result or blocker and avoid restarting uncertain work.
    What happens nextCheck the actual completed result or blocker before treating the approved task as delivered.
    06

    Check the completed response

    Check the completed response — actual Bruno interface with fictional example data
    Atelier Demo · Example account and simulated responses. Open the picture to zoom.
    1. 1The delivered conversation entry.
    2. 2The concrete completion response and website address.
    1. Open the latest delivery message in the dashboard history. It names the changed section, date, time and button, and supplies the website address.
    2. Read any limitations or requests for further information. A finished response should describe the work you actually approved.
    3. Open the result and inspect it yourself. The dashboard stores message text; your email may provide a clickable website link.
    What happens nextYou have a result to inspect and can reply with precise feedback.
    07

    Open the result from the same email thread

    Open the result from the same email thread — actual Bruno interface with fictional example data
    Atelier Demo · Example account and simulated responses. Open the picture to zoom.
      1. The completion email says “The designer has finished…” and lists the changes. It also confirms the items that stayed intact.
      2. Choose Open your website to inspect the result. Our example link opens an illustrative local website; this was not a live build.
      3. Reply with your feedback if needed. You do not have to begin a new ticket to ask the designer for a small correction to this work.
      What happens nextYou can move from the delivered email to the actual work and back to the same conversation.
      08

      Inspect the changed section, not just the message

      Inspect the changed section, not just the message — actual Bruno interface with fictional example data
      Atelier Demo · Example account and simulated responses. Open the picture to zoom.
      1. 1The approved new headline.
      2. 2The factual date and time.
      3. 3The button we will ask to refine.
      1. Check the welcome-section headline, 23 October date, 9–10:30 AM time and studio button. Compare these against the approved proposal.
      2. Also check the preserved items you named. In a real job, inspect navigation, images and other pages rather than assuming they are unchanged because the email says so.
      3. This fictional result makes the review concrete. We decide the button should say Come for a coffee instead and send that one change as a reply.
      What happens nextYour feedback can identify one exact change while keeping the rest of the approved work.
      09

      Request a precise revision in the same ticket

      Request a precise revision in the same ticket — actual Bruno interface with fictional example data
      Atelier Demo · Example account and simulated responses. Open the picture to zoom.
      1. 1Your specific button-only feedback.
      2. 2The completed revision response within the continuing conversation.
      1. Use Reply in the delivery thread. Our feedback says: “Make the button say Come for a coffee instead. Leave date, time, layout and every other page as they are.”
      2. The example history shows that feedback and the designer’s response together. There is still one saved request ticket.
      3. When a revision needs further approval or information, follow the actual reply. Do not assume every follow-up skips the service’s existing approval checks.
      What happens nextConcierge retains the task context while taking the correction back to the designer.
      10

      Verify the revision before closing the job

      Verify the revision before closing the job — actual Bruno interface with fictional example data
      Atelier Demo · Example account and simulated responses. Open the picture to zoom.
      1. 1The revised button wording.
      2. 2The headline stays unchanged.
      1. Open the result again. The button now says Come for a coffee. Confirm that the headline, date, time and layout still match the earlier version.
      2. If the result is right, reply to confirm or continue with another specific request. Explain unexpected changes rather than accepting an inaccurate result.
      3. This example changes one button only. It does not prove a real customer site was built or revised during documentation.
      What happens nextYou have checked both the correction and the parts that were meant to remain intact.
      11

      Decide whether WordPress needs this history

      Decide whether WordPress needs this history — actual Bruno interface with fictional example data
      Atelier Demo · Example account and simulated responses. Open the picture to zoom.
      1. 1The intentional, optional history-sharing choice.
      1. The sharing box starts unchecked in this example. Email requests still work without turning it on.
      2. Enable it only if you want your own connected WordPress chat to use your Concierge conversation as context.
      3. This setting is not a new WordPress connection, a grant of access to other customers or a replacement for proposal and approval checks.
      What happens nextYou can keep the workflows separate or explicitly choose shared context.
      12

      Wait for the shared-context confirmation

      Wait for the shared-context confirmation — actual Bruno interface with fictional example data
      Atelier Demo · Example account and simulated responses. Open the picture to zoom.
      1. 1The selected sharing preference.
      2. 2The explicit saved confirmation.
      1. Select the box and wait for Saved. Your next WordPress chat will use your shared Concierge. The setting request is simulated here.
      2. To turn it off again, clear the box and wait for the confirmation that the regular website designer will be used.
      3. If Could not save appears, retry after resolving the error. A click without a saved confirmation is not proof that the preference changed.
      What happens nextThe next applicable WordPress chat uses the preference you intentionally saved.
      13

      Recognize an account without active access

      Recognize an account without active access — actual Bruno interface with fictional example data
      Atelier Demo · Example account and simulated responses. Open the picture to zoom.
      1. 1The current inactive-access label.
      2. 2History sharing is disabled without active access.
      1. Concierge is not active on this account means the page is informational for this account. The sharing control is disabled.
      2. Check the account and service activation before expecting requests to run. Relevant tools still need their own permissions and available credits.
      3. Contact support if you expected access. Opening a marketing app preview, this page or an email draft does not itself activate a paid service.
      What happens nextOnce eligible access and tools are ready, use the active email workflow described in this guide.
      Keep this guide handy

      Come back whenever you need it.

      Use Quick guide for a short reminder of the main controls. Keep this full manual for the complete task and its different choices.

      In your dashboard, choose Quick guide → Show me around to replay the short tour. Use Read the guide or Download PDF for these complete instructions.

      Need help? Email help@iambruno.com with the service name and what happened. Do not send passwords or connection keys.