A spoken method for briefing, drafting, and reviewing social posts by voice.

Voice Prompting for Social drafts works best when the brief is short enough to say in one breath. Name the channel, the audience, the one idea the post should land, and the action you want. Add the occasion and the tone: a launch announcement and a lesson learned need different openings. Say what proof you can offer, such as a customer quote, a number you can defend, or a description of a screenshot. Then state the length and the format. A brief with all six parts produces a usable draft on the first pass, while a request to write something good about the launch produces a slogan.
Write the brief as a sequence you repeat every time: channel, audience, idea, proof, action, tone, length. The repeated order matters because it lets you dictate quickly and it lets a teammate take over without guessing. Say the idea as a single sentence in plain language, then say what the reader should know after reading it. If you cannot state the idea in one sentence, the post is not ready to be written. Ask the assistant to restate the idea in its first line before drafting, and correct the restatement if it is off. Ask for the restatement before the draft so a wrong idea costs one sentence rather than a rewrite.
Separate the substance from the style in the brief. Substance includes the claim, the proof, the audience, and the action. Style includes the opening, the rhythm, the emoji policy, and the level of formality. State the substance first and confirm that the assistant has it, then speak the style. When the two are mixed, a stylish opening can hide a missing claim, and the draft reads well while saying little. Ask for a one-line summary of the substance before any draft. This check takes seconds and catches the most common reason a post needs a full rewrite. Store the check with the brief so the next writer runs it too.
Define what the draft must not include. No invented statistics, no customer names without permission, no claims about competitors, and no promises about dates that are not confirmed. Add any house rules, such as spelling out acronyms on first use or avoiding exclamation marks. State these as prohibitions with a reason, because a rule with a reason survives when the brief is adapted for a new channel. Ask for a short list of anything the draft could not verify. A social draft that flags its own gaps is easier to approve than one that sounds confident and hides the missing proof.
Read the opening aloud before you judge the rest. A hook that looks fine on the page often sounds hollow when spoken, and a plain line can sound sharper than expected. Ask for three openings with different strategies: a direct claim, a question, and a short scene. Read each one aloud at normal speed. Keep the one you would say to a colleague without embarrassment. This test is fast and it uses the same skill you need for the rest of the post. Discard the openings that depend on wordplay you would never use in speech. If none of the three survives the read, rewrite the idea rather than the opening.
Ask for the body to follow one structure: claim, evidence, implication, action. This order keeps the post from drifting into background. Say how many sentences each part may take, so the structure is visible without counting. Then read the body aloud and mark the sentence where your attention drops; that is usually where the background starts. Ask for a revision that cuts everything before the claim. Social posts lose readers at the first sentence that feels like a preamble, and the spoken test finds that sentence faster than a silent read. Keep the claim sentence at the top of the revision request, so the body has an anchor.
Use the read-aloud pass to catch rhythm problems. Long sentences with several clauses are hard to say and harder to scan. Ask for shorter sentences and one idea per line where the channel allows line breaks. Read the draft at the pace of a conversation, not a presentation. If you run out of breath, the sentence is too long. Mark the places where you naturally pause and ask for line breaks there. Rhythm is not decoration; it controls whether a reader finishes the post or scrolls past the third line. Read the final version aloud once more after the line breaks are added.
Test the closing line separately. Ask for three closings: a question, a direct invitation, and a quiet statement. Read each aloud and notice which one you would actually answer. The closing should follow from the body rather than introduce a new idea. If the call to action requires a context the post has not set up, the body is missing a step. Ask for the closing to name the action in plain verbs. Keep the version that a reader could act on without re-reading the post. Ask for the action to be specific enough that a reader knows what happens next.
Ask for variants instead of one perfect post. Three variants with different openings and the same substance give you a real choice and reveal which angle is strongest. Label them by strategy, not by quality: direct, story, question. Read all three aloud and pick the one that fits the channel and the moment. Keep the other two; they are useful for a follow-up post or a different audience. Variants cost little and they prevent the slow loop of asking for small edits to a single draft that was never the right shape. Three variants take less time than three rounds of edits on the wrong draft.
Change one variable at a time when you compare variants. If one version has a different opening and a different length, you cannot tell which change made it better. Ask for variants that differ in opening only, then in length only. Compare them by the response you expect, not by personal taste. Say the expected response in the brief: a reply, a click, a share, or a saved post. When the goal is explicit, the choice between variants becomes a small test rather than a debate about style. Keep the variant labels in the brief so the choice is easy to repeat later.
Adapt length to the channel rather than to habit. Ask for a short version, a medium version, and a single-line version of the same idea. Write the single line first, because it forces the idea into its smallest form. Then expand only where the channel rewards detail. Read the short version aloud and ask whether it still contains the proof and the action. A post that loses its proof when shortened was carrying too much background. Keep the three lengths together so the next post starts from a tested range. Compare the three versions after a week to see which length your audience responds to.
Use a variant to test the opening claim. Write one version that states the conclusion first and one that starts with the situation. Readers who already care about the problem respond to the situation; readers who are scrolling respond to the conclusion. Pick based on what you know about the audience, and record the choice in the brief. When you post both at different times, note which drew more replies and why you think so. Over a few cycles, this record becomes a practical guide to openings that work for your audience. Review the record once a month and update the opening guidance in the brief.
Voiskey keeps the drafting and the review in the same field. Press the shortcut, speak the brief, and the polished text appears at the insertion point in the app you are using. Then read the draft aloud and use the same tool for revision: speak the sentence you want changed and dictate the replacement. Because filler words, stutters, and false starts are removed, the revision reads like an instruction rather than a transcription. The speak, polish, type, and edit loop means a post can be briefed, drafted, and revised without leaving the drafting field. Save the approved post beside the brief so the next draft starts from an example.
Ask a colleague to read the draft without your brief and tell you what they think it says. If their summary differs from your one-sentence idea, the draft is ambiguous. Give them the intended audience and ask which sentence they would cut. Two readers often agree on the weak line, which makes the edit easy to justify. Record their summary next to the draft so you can compare it with the posted version. A second reader is the cheapest check against a post that only makes sense to the person who wrote it. Choose the reviewer for the audience, not for seniority, and ask for one change only.
Check every factual claim against a source you can open. Numbers, dates, product names, and quoted customers each need a link or a document. Ask the draft to mark claims it cannot source, and treat those marks as blockers rather than notes. Replace an unsourced claim with a narrower one you can defend, or remove it. Read the post once more after the replacement to confirm the argument still holds. A short post with two solid claims is more persuasive than a long one with five that a reader could question. Keep the source list with the draft so a later edit does not reintroduce a removed claim.
Do a final read on the device where you will publish. Line breaks, emoji, and links behave differently across screens, and a post that looks fine in a wide window can look cramped on a phone. Read the post aloud one last time and fix any sentence you stumble over. Confirm that the first line makes sense without the rest, because many readers see only that line. Check that the closing action is clear. When the draft passes these three checks, stop editing; further passes tend to flatten the voice without improving the post. Send the final version to the approved example list if it performed well.
Keep a spoken brief for each channel you use. Each brief stores the audience, the typical length, the tone, the format, and the house rules for that channel. Speak the brief at the start of a session and add the specific idea and proof. A small set of channel briefs removes the repeated work of explaining the same context every time. Review them when the channel changes its format or when your audience shifts. Name each brief by the audience and the goal, not by the platform, so the set stays useful when the channels change. Keep the brief to one page and read it aloud before the first post of the week.
Share the channel briefs with the team and agree on one owner for each. The team plan offers shared vocabulary and workflows, so product names, campaign labels, and house rules stay consistent when several people draft. Store the briefs with one approved example per channel, so a new writer can see the standard. Ask each writer to read the example aloud before drafting, because the spoken version reveals the intended rhythm. When two drafts disagree in tone, compare the briefs before rewriting either one. Keep a short log of tone disagreements and their resolution, so the brief learns from every correction instead of repeating the same debate.
Voiskey supports more than one hundred languages and translation, so you can speak the brief in the language you think in and ask for a draft in the language your audience reads. Keep product names and handles unchanged, and ask for a back translation when the wording carries a claim. Review the translated draft with a fluent speaker, because humor and idiom rarely survive a direct translation. Store the approved version with the brief so the next post starts from a tested example rather than a literal translation. Note the reviewer and the date so a later claim can be tied to a specific check.
Download Voiskey for Mac and Windows and dictate the next post from the channel brief. Speak the idea, the proof, and the action in one pass, then read the draft aloud and cut the sentence where your attention drops. Keep the brief and the approved example together for the next session. After a few posts, review which brief fields you actually used and remove the rest. A brief that matches how you really write is easier to keep than a template that looks complete and slows you down. Add one line to the brief after each post that records what you changed and why.
Voiskey is an AI voice typing app. Press a shortcut, speak the channel, audience, idea, proof, and action, and the text appears at the insertion point in the app you are using. Filler words, stutters, and false starts are removed, and punctuation and formatting are adapted to the brief.
Yes. Voiskey adapts punctuation, formatting, tone, and wording to what you are trying to do. Say the channel and the reader in the brief, then ask for a version that fits. A short line for a fast feed and a longer post for a professional group can come from the same idea.
Voiskey learns names, jargon, acronyms, and spelling preferences, so campaign labels and product names stay consistent across drafts. Say them once in the channel brief and reuse it. The app places the polished draft at your insertion point with the spellings you prefer, which reduces cleanup before review.
Voiskey supports more than one hundred languages and translation. You can dictate the brief in one language and ask for the post in another, then request a translation back for review. Keep product names unchanged and have a fluent speaker check idiom, because humor rarely survives a direct translation.

Download Voiskey for Mac and Windows and dictate your next social draft.
Use it across macOS, Windows, iOS, and Android