[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-post-zh-\u002Fhow-to-write-an-sop":3,"blog-posts-zh":786,"related-docs-zh-":1623},{"page":4,"surround":780},{"id":5,"title":6,"authors":7,"body":10,"date":751,"demo-cta":752,"description":753,"extension":754,"genre":755,"heroOrder":756,"icp":757,"image":760,"meta":761,"navigation":762,"no-translate":752,"path":763,"preview":756,"rank-country":756,"rank-keywords":764,"rank-tag":773,"related":756,"seo":774,"shelf":775,"stem":776,"topic":777,"updated":756,"video":778,"__hash__":779},"blog\u002Fblog\u002Fhow-to-write-an-sop.md","How to write an SOP: steps, template, example, review cycle — and where the SOP lives after it is written (2026)",[8],{"name":9},"The Mind.com Team",{"type":11,"value":12,"toc":738},"minimark",[13,17,40,44,47,52,55,64,68,74,80,98,104,133,139,145,149,280,283,287,290,441,444,448,451,460,471,477,481,484,570,583,587,590,601,609,629,632,636,641,644,649,652,657,660,665,668,673,676,681,684,689,692,695],[14,15,6],"h1",{"id":16},"how-to-write-an-sop-steps-template-example-review-cycle-and-where-the-sop-lives-after-it-is-written-2026",[18,19,20,28,34],"ul",{},[21,22,23,27],"li",{},[24,25,26],"strong",{},"Seven steps:"," scope one job, watch it done, draft the steps first, add the branches, test on a newcomer, approve and version, publish where the team reads.",[21,29,30,33],{},[24,31,32],{},"The document outlives the writing:"," in Teams, Zoom, Google Workspace and Slack the SOP is a file in one language, retyped by hand after each review.",[21,35,36,39],{},[24,37,38],{},"InterMIND keeps the SOP and every review of it in each member's language,"," next to those tools rather than instead of them. Guests join free by link, no account; you pay only for active members.",[41,42,43],"p",{},"A standard operating procedure, or SOP, is the agreed way one recurring job is done in your organization: the steps in order, who takes each, what each step leaves behind, and what to do when the normal path is blocked. Writing one is not a writing task. It is an observation task with a document at the end — the words are the easy part, and most SOPs that fail were written by someone who skipped the watching.",[41,45,46],{},"This guide is the writing process in order — which job to pick, how to watch it, how to draft the steps, how to test the draft, how to approve and publish it — then a one-page template, a worked example, and the review cycle that turns a first version into a procedure the team actually runs. The last part is where the document lives after it is written: in the tools your team already uses, and in the place the people who do the job already read. Because an SOP is judged on the Tuesday a new colleague opens it alone, not on the day it was approved.",[48,49,51],"h2",{"id":50},"which-jobs-get-an-sop-and-which-dont","Which jobs get an SOP — and which don't",[41,53,54],{},"Four signals say a job deserves a procedure. It recurs: weekly or daily, not once a year. More than one person does it, or will — a job done by one person for years is in their head, and the SOP is written the month before they go on leave. The cost of doing it differently is real: a complaint answered two ways, a shipment with the wrong documents, a patient file opened under the wrong name. And it has hand-offs — the moment the work passes from reception to the agent, from sales to logistics, is where the steps go missing.",[41,56,57,58,63],{},"Three things do not get an SOP. A job that crosses three teams end to end is a process; map it as stages, then write one SOP per stage and role. A single screen or form is a work instruction, which lives under the SOP step that uses it and is rewritten when the software changes, so that the SOP is not. And a judgment — pricing a custom order, deciding whether a complaint is justified — gets a policy with limits and a named decider, not numbered steps that pretend there is no judgment. The five kinds of document, side by side, are in the ",[59,60,62],"a",{"href":61},"\u002Fblog\u002Fsop-template","SOP template"," guide; what follows assumes you have picked one job, one role at a time.",[48,65,67],{"id":66},"how-to-write-an-sop-seven-steps","How to write an SOP: seven steps",[41,69,70,73],{},[24,71,72],{},"1. Pick one job and draw its edges."," Name it with a verb and an object — \"Onboarding a new distributor\", not \"Distributors\" — and write two sentences before anything else: where it starts (the trigger: a signed agreement, a phone ringing, 07:30 on a weekday) and where it ends (the result that now exists: a first order confirmed, a complaint closed, the doors open). Everything between those two sentences is the SOP; everything outside them is another document. If the job has no clear end, it is two jobs. Leave the purpose sentence for later: you will know what the procedure is for once you have seen it done.",[41,75,76,79],{},[24,77,78],{},"2. Watch the job being done — twice."," By the person who does it, not the person who manages it, and at the real counter or screen, not in a meeting room. Write down what happens, including the spreadsheet on the side and the colleague who gets called at step 4; ask at every step, \"and what do you do when this fails?\" — the answers are the exceptions section, and nobody volunteers them unasked. Watch a second time with a different person or on a different day. Where the two runs differ is the reason the SOP exists; decide for each difference whether it is a step to fix in the document or a conversation to have with the team.",[41,81,82,85,86,90,91,90,94,97],{},[24,83,84],{},"3. Draft the steps first, header last."," Open the template at the procedure section and write the steps as you saw them: one action per step, in the order it happens, each starting with a role and a verb in the present tense — \"Reception logs…\", \"The account owner sends…\" — and each ending in a result a second person could check: the register entry, the sent email, the confirmed order. Three columns help: ",[87,88,89],"em",{},"who",", ",[87,92,93],{},"does what",[87,95,96],{},"result or record",". A step that needs a paragraph is two steps or a work instruction. Aim for a document that reads in five minutes; the detail lives in the linked instructions. Choose the shape for the steps now — a numbered list for under ten steps with no branches, numbered steps with lettered sub-steps when a step has a sequence inside it, a flowchart when the branches matter more than the order, a checklist when the question is \"did we\" rather than \"how\".",[41,99,100,103],{},[24,101,102],{},"4. Add the branches: exceptions, escalation, records."," For every step, the condition under which it cannot be done as written, and what happens then — with a role or a person who decides, never \"ask someone\". Close the list with one line that covers what you missed: \"Anything not covered here: the team lead decides, and the case is raised at the next review.\" Then the records: what exists at the end of the procedure that did not exist at the start, where it is kept, for how long. This is the section an auditor reads, and the one that tells you afterwards whether the procedure was followed.",[41,105,106,109,110,113,114,117,118,121,122,125,126,129,130,132],{},[24,107,108],{},"5. Fill in the header and the sections around the steps."," Now the purpose is one sentence you can write: what this procedure achieves and what goes wrong without it. Scope says when it applies and when it does not, naming the neighbouring SOPs by ID. Roles are the roles that appeared in the steps — roles, not names, so the document survives a hire. Prerequisites are what must be in place before step 1. The header is five fields: an ",[24,111,112],{},"ID"," people can cite, ",[24,115,116],{},"version"," 1.0, an ",[24,119,120],{},"owner"," who is one person, the ",[24,123,124],{},"effective date"," and the ",[24,127,128],{},"next review date",". A procedure without a review date is reviewed when something goes wrong. The full eight-section format, with the longer template and the reasoning behind each section, is in ",[59,131,62],{"href":61},".",[41,134,135,138],{},[24,136,137],{},"6. Test it on someone who has never done the job."," Give them the document and nothing else, and sit behind them. Every place they stop is a missing step, a missing definition or a missing exception; every place they ask you a question is a sentence to add. One test with a new person is worth three reviews by experienced ones, who fill the gaps without noticing them. If the first test produced more than three changes, test once more with someone else. The owner approves after the test, not before — a draft that has not been run is an opinion.",[41,140,141,144],{},[24,142,143],{},"7. Approve, version, publish where the team reads — and date the review."," The owner signs off, the version becomes 1.0, and the draft is kept, not deleted. Publish the SOP in the place the people who run the procedure already talk, not in a folder with forty others that only the people who already know the job can find; announce it with the three lines that matter most to the people reading it. The same day, put the next review date in the calendar, and write down the four events that bring the review forward: an incident the procedure did not prevent, a change in the tool or form the steps depend on, a change in the rule it implements, and three people doing a step differently from the document, which is a vote, not a discipline problem.",[48,146,148],{"id":147},"a-one-page-sop-template","A one-page SOP template",[150,151,152,176,211,246,262],"blockquote",{},[41,153,154,157,160,163,164,167,168,171,172,175],{},[24,155,156],{},"[SOP ID] — [Procedure name]",[158,159],"br",{},[24,161,162],{},"v[1.0]"," · ",[24,165,166],{},"Owner:"," [name, role] · ",[24,169,170],{},"Effective:"," [date] · ",[24,173,174],{},"Next review:"," [date]",[41,177,178,181,182,184,187,188,191,192,194,197,198,201,202,204,205,207,210],{},[24,179,180],{},"Purpose:"," [one sentence — what this procedure achieves, and what goes wrong without it]",[158,183],{},[24,185,186],{},"Applies to:"," [trigger, situations, sites] · ",[24,189,190],{},"Not:"," [what another SOP covers, with its ID]",[158,193],{},[24,195,196],{},"Roles:"," ",[24,199,200],{},"[Role]"," — [what it is accountable for] · ",[24,203,200],{}," — [what it is accountable for]",[158,206],{},[24,208,209],{},"Before step 1:"," [access, tools, templates, lists]",[41,212,213,216,218,221,222,225,227,221,230,232,234,221,237,239,241,221,244],{},[24,214,215],{},"Steps",[158,217],{},[24,219,220],{},"1."," [Role] [does what] → ",[87,223,224],{},"[result or record]",[158,226],{},[24,228,229],{},"2.",[87,231,224],{},[158,233],{},[24,235,236],{},"3.",[87,238,224],{},[158,240],{},[24,242,243],{},"4.",[87,245,224],{},[41,247,248,251,252,254,251,256,258,261],{},[24,249,250],{},"If [condition]:"," [what to do, who decides]",[158,253],{},[24,255,250],{},[158,257],{},[24,259,260],{},"Anything not covered here:"," [role] decides; the case is raised at the next review.",[41,263,264,267,268,270,273,274,276,279],{},[24,265,266],{},"Records:"," [what exists at the end, where it is kept, for how long]",[158,269],{},[24,271,272],{},"References:"," [policy it implements, related SOPs, work instructions]",[158,275],{},[24,277,278],{},"History:"," v1.0 — [date] — first issue — approved by [name]",[41,281,282],{},"The template is plain text with bold labels, so it pastes into a Word file, a Google Doc, a wiki page, a Slack canvas or a chat note without reformatting. It is deliberately one page: the two sections most often skipped when a template is long are the exceptions and the review date, and those are the two that decide whether the document is still true in a year.",[48,284,286],{"id":285},"a-worked-example-onboarding-a-new-distributor","A worked example: onboarding a new distributor",[41,288,289],{},"An exporter with distributors in three countries; the job passes through four roles and ends when the distributor's first order is confirmed.",[150,291,292,311,349,412],{},[41,293,294,297,299,163,302,304,305,307,308,310],{},[24,295,296],{},"SOP-SA-03 — Onboarding a new distributor",[158,298],{},[24,300,301],{},"v1.2",[24,303,166],{}," Export manager, Chiara B. · ",[24,306,170],{}," 15 Oct 2026 · ",[24,309,174],{}," 15 Apr 2027",[41,312,313,315,316,318,320,321,323,324,326,197,328,331,332,335,336,339,340,343,344,346,348],{},[24,314,180],{}," A new distributor can place its first order within ten working days of the signed agreement, with prices, documents and a named contact on both sides.",[158,317],{},[24,319,186],{}," Every distributor agreement signed by the export manager. ",[24,322,190],{}," agents on commission (SOP-SA-05); an existing distributor adding a territory (SOP-SA-04).",[158,325],{},[24,327,196],{},[24,329,330],{},"Export manager"," — signs, assigns the account owner, decides credit terms. ",[24,333,334],{},"Account owner"," — runs steps 3 to 7. ",[24,337,338],{},"Finance"," — credit check and customer record. ",[24,341,342],{},"Logistics"," — shipping profile.",[158,345],{},[24,347,209],{}," the signed agreement in the contracts folder; the price list for the territory; the onboarding pack in the distributor's language.",[41,350,351,353,355,357,358,361,363,365,366,369,371,373,374,377,379,381,382,385,387,390,391,394,396,399,400,403,405,408,409],{},[24,352,215],{},[158,354],{},[24,356,220],{}," The export manager assigns an account owner within one working day of signature → ",[87,359,360],{},"assignment noted in the distributor's record",[158,362],{},[24,364,229],{}," Finance runs the credit check and opens the customer record → ",[87,367,368],{},"credit limit and payment terms in the record",[158,370],{},[24,372,236],{}," The account owner sends the onboarding pack — price list, order form, product sheets, the two contacts on our side — in the distributor's language → ",[87,375,376],{},"pack sent; date and recipients logged",[158,378],{},[24,380,243],{}," The account owner holds the kickoff call with the distributor's sales and order staff: how to order, lead times, who answers which question → ",[87,383,384],{},"call recap in the record; open questions with owners",[158,386],{},[24,388,389],{},"5."," Logistics sets up the shipping profile — incoterms, carrier, the documents the destination requires → ",[87,392,393],{},"profile active",[158,395],{},[24,397,398],{},"6."," The account owner places a test order with the distributor on the line → ",[87,401,402],{},"first order confirmed, or the blocking step named",[158,404],{},[24,406,407],{},"7."," The account owner books the 30-day review with the distributor → ",[87,410,411],{},"calendar entry, both sides invited",[41,413,414,417,418,421,422,425,426,428,430,431,433,435,436,438,440],{},[24,415,416],{},"If the credit check fails:"," step 2 stops; the export manager decides prepayment or decline within two working days. ",[24,419,420],{},"If the pack does not exist in the distributor's language:"," send the English pack, raise the gap at the next review, do not postpone the kickoff call. ",[24,423,424],{},"If the test order fails:"," the blocking step is written into the record and fixed before the 30-day review.",[158,427],{},[24,429,266],{}," the distributor's record (kept for the life of the agreement plus five years), the kickoff call recap, the test order.",[158,432],{},[24,434,272],{}," Export policy §2; SOP-SA-04; SOP-SA-05; WI-SA-03a \"The distributor record\".",[158,437],{},[24,439,278],{}," v1.2 — 15 Oct 2026 — kickoff call added as step 4; test order moved before the 30-day review — approved by Chiara B. · v1.1 — 2 Jun 2026 — shipping profile made its own step — approved by Chiara B. · v1.0 — 10 Jan 2026 — first issue.",[41,442,443],{},"Notice what the example does. Every step starts with a role and a verb and ends in something a second person could check. Each exception names who decides. The history explains why the steps are in this order — step 4 exists because a reviewer found that distributors who never had the call placed their first order late. And one step is not a document at all: step 4 is a call, with the distributor's staff on the other side of it, and what that call leaves behind is the part of the procedure no template can hold.",[48,445,447],{"id":446},"the-review-cycle-the-first-version-is-a-draft-that-worked-once","The review cycle: the first version is a draft that worked once",[41,449,450],{},"An SOP is a claim about how work is done, and the work moves. Three things keep the claim honest after publication, and they belong to the writing process, not to some later maintenance phase.",[41,452,453,456,457,459],{},[24,454,455],{},"A date, and the triggers that beat it."," Six or twelve months is usual, shorter for anything regulated or safety-related; the four events from step 7 bring the review forward. The review is a twenty-minute meeting: the owner and two or three people who run the procedure, the current version on everyone's screen, the same four items every time — deviations since the last review, incidents the procedure touched, steps to change, add or delete with the reason, and the decision to reissue as a new version or confirm unchanged with a new date. The review agenda, written out, is in the ",[59,458,62],{"href":61}," guide.",[41,461,462,465,466,470],{},[24,463,464],{},"A new version, with the old one kept."," The edit becomes one line in the history — date, what changed, who approved — and the version number moves: a changed step is a minor version, a changed scope or a new role a major one. The previous version is marked superseded and kept; a colleague explaining what happened in March needs the procedure as it was in March. A review decision that changes a rule rather than a step is also an entry in the ",[59,467,469],{"href":468},"\u002Fblog\u002Fdecision-log-template","decision log",", with the SOP ID in it.",[41,472,473,476],{},[24,474,475],{},"The people who do the job hear about it."," A reissued SOP that nobody announced is the old SOP with a new number. The change goes to the people who run the procedure, in the place they already read, with the lines that changed quoted — and the new review date goes in the calendar the same day. Where that place is, and what the review meeting leaves behind in it, depends on the tools the team runs on.",[48,478,480],{"id":479},"where-the-sop-lives-after-it-is-written-the-tools-you-already-use","Where the SOP lives after it is written: the tools you already use",[41,482,483],{},"The document itself lives wherever the team's documents live — a Word file in a shared library, a Google Doc, a page in a wiki, a canvas in a channel. The review is a meeting, and each platform has a place for what the review meeting leaves behind; each stops at a different point. Documented behaviour only, from the vendors' own pages, with the month each page was checked:",[485,486,487,503],"table",{},[488,489,490],"thead",{},[491,492,493,497,500],"tr",{},[494,495,496],"th",{},"Platform",[494,498,499],{},"Where the review of the SOP is noted during the call",[494,501,502],{},"What of the review comes back after the call",[504,505,506,527,540,557],"tbody",{},[491,507,508,514,524],{},[509,510,511],"td",{},[24,512,513],{},"Microsoft Teams",[509,515,516,519,520,523],{},[87,517,518],{},"Notes"," in the meeting controls — a Loop component that any attendee or organizer can edit, with tasks assigned by tagging people; or ",[87,521,522],{},"Add an agenda"," in the meeting's Details when scheduling",[509,525,526],{},"Saved automatically and reachable from the Teams calendar and the meeting recap; what is in the notes is what a person typed; external attendees cannot access or edit them (checked October 2026)",[491,528,529,534,537],{},[509,530,531],{},[24,532,533],{},"Zoom Workplace",[509,535,536],{},"Meeting summary with AI Companion is generated from the meeting, in three sections — quick recap, summary, next steps — on paid Zoom Workplace plans; a person's own notes are a separate document",[509,538,539],{},"The summary is sent by email, listed on the Summaries page of the web portal and can be posted to the meeting's group chat in Team Chat; participants receive it when the host chose to share it, only the host can edit it, and unauthenticated users do not receive the email (checked August 2026)",[491,541,542,547,554],{},[509,543,544],{},[24,545,546],{},"Google Workspace",[509,548,549,550,553],{},"The Calendar event's description, or a Google Doc linked from it; on eligible Workspace editions and Google AI plans, ",[87,551,552],{},"Take notes for me"," can be switched on in Calendar when the event is created",[509,555,556],{},"The notes arrive as a Google Doc after the meeting, shared with all guests, organization guests or hosts only, per the setting; the feature supports one language at a time — multiple languages spoken in the same meeting are not supported (checked October 2026)",[491,558,559,564,567],{},[509,560,561],{},[24,562,563],{},"Slack",[509,565,566],{},"A canvas from a template, shared in the channel, with sections for objectives, next steps and action items with due dates",[509,568,569],{},"The canvas stays in the channel as a document; what was said in the call is not in it unless someone types it (checked October 2026)",[41,571,572,573,577,578,582],{},"Two things are the same everywhere. The SOP is a document in the one language it was written in, and what the review changed reaches it only when a person types it in afterwards. The translation these suites document belongs to the call, not to the document: Microsoft documents live translated captions in Teams meetings when the organizer holds a Teams Premium or Microsoft 365 Copilot license, and Google documents translated captions in Meet on eligible Workspace plans (both checked August 2026) — what each covers and where each stops is in ",[59,574,576],{"href":575},"\u002Fblog\u002Fteams-live-translation","Microsoft Teams live translation"," and ",[59,579,581],{"href":580},"\u002Fblog\u002Fgoogle-meet-live-translation","Google Meet live translation",". The procedure a colleague opens on Tuesday, and the review that changed it, are separate objects from those captions, and they are read in the language they were typed in.",[48,584,586],{"id":585},"how-the-sop-its-review-and-its-history-stay-readable-for-every-member","How the SOP, its review and its history stay readable for every member",[41,588,589],{},"InterMIND is a communication space where a team's work lives in a channel, so the finished SOP has an obvious home: the channel of the team that runs the procedure. Posted as a note — a rich-text message with headings and numbered lists, edited later from its own menu — it is read by each member in their own language with the original a toggle away, and pinned so the current version is the first thing a new colleague finds; a reader who switches on edit history sees the earlier wording of a changed step as a word-level diff with its timestamp. Uploaded as a file — a PDF or a Word document — it carries, on every plan, an AI summary in the reader's language with each point linked to the paragraph it came from, so the five-minute read exists before anyone has written it; on paid plans the file itself opens translated into the reader's language (30 languages for documents). If the master copy stays in a document tool, its updates land in the channel by email: the channel's host gives it an address of its own, and a message sent there appears as a regular message with the sender named and attachments kept.",[41,591,592,593,596,597,600],{},"The review meeting starts from that channel, and so does the kickoff call in the example above. During the call, the current version goes on everyone's screen next to the video tiles with ",[87,594,595],{},"Share to conference"," — a note, or a Google Docs or OneDrive document linked in the chat — and each participant scrolls it independently and reads it in their own language; a shared note is edited live by the sharer while the room watches the changed step take shape. When the call ends, the recap is written from the meeting itself — a summary, the points marked agreed, open or disputed, the action items with owners, each line keeping its timestamp — and the documents shared during the session contribute their summaries alongside what was said. It arrives by email, as a message in the channel and as a link in the calendar event, and every signed-in member reads it ",[24,598,599],{},"in their own language",": the record is translated per reader, not written once in the language the room happened to use. Any member can edit it, every edit keeps author and revision history, and the channel keeps the recap of every past session — so the review that produced v1.2 is one click from the note that is v1.2. A member's own assistant — Claude, ChatGPT, Copilot or Gemini, connected through the MCP connector — searches recaps, transcripts, chats and the text of shared files in one question, \"what did we change in the distributor onboarding procedure, and why?\", and reads the document itself; this runs for organizations with AI features on. Set next to the table above, the difference is a plain statement of fact: the captions those suites document translate the call while it runs; here the procedure, its review and its history are one record, read by each member in their own language.",[41,602,603,604,608],{},"The people who run a procedure are not always employees. A distributor's order staff, a contractor, a locum: an external member of the channel joins by email onto a free account and reads the SOP and its history like everyone else; a person without an account is a guest of one meeting — they join the kickoff or the review call by link, from a phone, at no cost, hear it live in their own language, and get no record afterwards. The host provides the space and, on a paid plan, pays only for the ",[59,605,607],{"href":606},"\u002Fpricing","members active in the previous 28 days"," — joined a meeting, wrote in a chat or asked the assistant; members who go quiet keep their access at no cost.",[18,610,611,620],{},[21,612,613,619],{},[24,614,615],{},[59,616,618],{"href":617},"\u002Ffeatures\u002Frecap","Open a complete recap"," — a real record rendered by the same code that writes yours.",[21,621,622,628],{},[24,623,624],{},[59,625,627],{"href":626},"\u002Fdemo","Try the live demo"," — no signup; speak, and hear the room translated per listener.",[41,630,631],{},"Writing an SOP as a craft survives every tool: somebody still has to watch the job being done, write the steps as actions a second person can check, and sit behind the new colleague on the first run. What doesn't have to survive is the second job — keeping a translated copy of every version by hand, and retyping what the review changed, in one language, for people who read others.",[48,633,635],{"id":634},"faq","FAQ",[41,637,638],{},[24,639,640],{},"How do you write an SOP?",[41,642,643],{},"Pick one recurring job done by one role and write where it starts and where it ends. Watch the person who does it, twice, and note every branch. Draft the steps first — one action per step, a role plus a verb in the present tense, a result a second person could check — then add the exceptions with a named decider and the records that exist at the end. Fill in the purpose, scope, roles and a header with an ID, a version, one owner and a review date. Test it on someone who has never done the job and fix every place they stop. Have the owner approve it, publish it where the team already reads, and put the review date in the calendar.",[41,645,646],{},[24,647,648],{},"What should be included in an SOP?",[41,650,651],{},"A header with the ID, version, owner, effective date and next review date; the purpose in one or two sentences; the scope, including what the SOP does not cover; the roles involved; prerequisites; the numbered procedure; exceptions and escalation with a person or role who decides; the records the procedure produces and where they are kept; and references with a revision history. Templates that carry only the header and the steps are the ones that fall out of date without anyone noticing.",[41,653,654],{},[24,655,656],{},"What is an example of an SOP?",[41,658,659],{},"Any recurring, multi-person job with a clear start and end: handling a customer complaint from logging to closure, opening a clinic or a shop in the morning, onboarding a new distributor from signed agreement to first order, releasing a batch, closing the month in finance. The worked example in this guide is distributor onboarding — seven steps across four roles, three exceptions, a history of three versions — and the complaint-handling and clinic-opening examples are in the SOP template guide.",[41,661,662],{},[24,663,664],{},"How long should an SOP be?",[41,666,667],{},"Short enough to read in five minutes before doing the job: one to two pages for most procedures, under ten steps if the format is a simple numbered list. If it is longer, either the job is two jobs, or the document is carrying detail that belongs in a work instruction under one of the steps — screenshots, field names, button labels — or justification that belongs in the policy above it.",[41,669,670],{},[24,671,672],{},"Who should write SOPs?",[41,674,675],{},"The person who does the job, with the owner of the procedure. The owner — a named person, usually the team lead or the manager of the area — is accountable for the document being true and for its review; the person who does the job is the co-author, because the SOP written about them instead of with them lives in a folder while the real procedure lives in their head. A newcomer to the job is the tester, not the author.",[41,677,678],{},[24,679,680],{},"What is the difference between an SOP and a process?",[41,682,683],{},"A process describes how work flows across roles and teams in stages and hand-offs — intake, triage, resolution, closure. An SOP describes how one of those stages is done by one role, step by step, with a result per step. A process map tells you where the SOPs are needed; one SOP tells one person what to do on Tuesday morning. Writing an SOP for a whole cross-team process produces a manual nobody opens at the counter.",[41,685,686],{},[24,687,688],{},"How often should an SOP be updated?",[41,690,691],{},"On the review date in its header — every six or twelve months is usual, shorter where the procedure is regulated or safety-related — and earlier when one of four things happens: an incident the procedure did not prevent, a change in the tool or form the steps depend on, a change in the rule it implements, or three people doing a step differently from the document. Each update is a new version with one line in the history saying what changed and who approved it; the old version is kept.",[693,694],"hr",{},[41,696,697],{},[87,698,699,700,706,707,706,712,706,717,706,722,706,727,706,732,737],{},"Sources: ",[59,701,705],{"href":702,"rel":703},"https:\u002F\u002Fsupport.microsoft.com\u002Fen-us\u002Foffice\u002Ftake-meeting-notes-in-microsoft-teams-3eadf032-0ef8-4d60-9e21-0691d317d103",[704],"nofollow","Microsoft — Take meeting notes in Microsoft Teams","; ",[59,708,711],{"href":709,"rel":710},"https:\u002F\u002Fsupport.microsoft.com\u002Fen-us\u002Foffice\u002Fuse-live-captions-in-microsoft-teams-meetings-4be2d304-f675-4b57-8347-cbd000a21260",[704],"Microsoft — Use live captions in Microsoft Teams meetings",[59,713,716],{"href":714,"rel":715},"https:\u002F\u002Fsupport.zoom.com\u002Fhc\u002Fen\u002Farticle?id=zm_kb&sysparm_article=KB0058013",[704],"Zoom — Using Meeting Summary with AI Companion",[59,718,721],{"href":719,"rel":720},"https:\u002F\u002Fsupport.google.com\u002Fmeet\u002Fanswer\u002F16909639?hl=en",[704],"Google — Calendar & Meet settings for \"Take notes for me\"",[59,723,726],{"href":724,"rel":725},"https:\u002F\u002Fsupport.google.com\u002Fmeet\u002Fanswer\u002F14754931?hl=en&co=GENIE.Platform%3DDesktop",[704],"Google Meet — \"Take notes for me\" in Google Meet",[59,728,731],{"href":729,"rel":730},"https:\u002F\u002Fsupport.google.com\u002Fmeet\u002Fanswer\u002F16221730",[704],"Google Meet — Use translated captions",[59,733,736],{"href":734,"rel":735},"https:\u002F\u002Fslack.com\u002Ftemplates\u002Fmeeting-agenda",[704],"Slack — Meeting agenda template (canvas)",". Microsoft, Google and Slack meeting-notes and template pages checked October 2026; the Zoom meeting-summary page and the Teams and Meet captions pages checked August 2026. Vendors change plans, features and language lists over time; check their pages for the current state.",{"title":739,"searchDepth":740,"depth":741,"links":742},"",2,3,[743,744,745,746,747,748,749,750],{"id":50,"depth":740,"text":51},{"id":66,"depth":740,"text":67},{"id":147,"depth":740,"text":148},{"id":285,"depth":740,"text":286},{"id":446,"depth":740,"text":447},{"id":479,"depth":740,"text":480},{"id":585,"depth":740,"text":586},{"id":634,"depth":740,"text":635},"2026-10-24",false,"To write an SOP, pick one recurring job, watch the person who does it, draft the numbered steps first — each starting with a role and a verb and ending in a result someone else can check — add the exceptions and the records, give it an ID, an owner and a review date, test it on someone new to the job, then publish it where the team already reads. The seven steps in order, a one-page template you can copy, a worked example, the review cycle that keeps the procedure true, where the SOP lives in Teams, Zoom, Google Workspace and Slack after it is written — and how the procedure and every review of it stay readable for each member in their own language.","md","seo",null,{"role":758,"spend":759},"team-lead","incumbent-subscription","\u002Fblog\u002Fhow-to-write-an-sop.svg",{},true,"\u002Fblog\u002Fhow-to-write-an-sop",[765,766,767,768,769,770,771,772],"how to write an sop","how to write a standard operating procedure","how to create an sop","sop writing","writing an sop","sop steps","sop example","sop format","wave-space",{"title":6,"description":753},"icp-work","blog\u002Fhow-to-write-an-sop","meetings","usecase-teams-meeting-shared-files","Fq0UH-0vwb_uUOGx1HBg3pLs6jjRQsYfN-hEXK5cnsM",[756,781],{"title":782,"path":783,"stem":784,"description":785,"children":-1},"How to delegate tasks: the handover that sticks — brief, owner, deadline, and a record both sides can read (2026)","\u002Fblog\u002Fhow-to-delegate-tasks","blog\u002Fhow-to-delegate-tasks","To delegate a task, hand over an outcome rather than a list of steps: a one-paragraph brief with the result, the deadline and the limits, one owner who says yes out loud, a check-in agreed before the work starts, and a handover kept where both sides can read it later. The method step by step, a brief template you can copy, a RACI chart for work that several people touch, what to delegate and what to keep, where the handover lives in Teams, Zoom, Google Workspace and Slack — and how the task comes back in the next recap as done or not done, in every member's own language.",[787,790,797,805,813,820,828,836,843,851,859,867,876,883,891,899,907,917,925,932,939,947,956,965,973,981,988,997,1004,1011,1018,1025,1032,1039,1046,1053,1060,1067,1074,1081,1088,1095,1102,1110,1117,1124,1132,1139,1147,1155,1162,1169,1176,1184,1192,1201,1208,1215,1222,1229,1236,1243,1250,1257,1265,1273,1280,1287,1295,1303,1310,1317,1324,1331,1338,1346,1354,1362,1370,1377,1385,1393,1400,1407,1415,1422,1429,1436,1443,1450,1457,1465,1472,1479,1486,1493,1501,1509,1517,1524,1531,1539,1545,1552,1560,1568,1576,1584,1591,1599,1607,1615],{"path":763,"title":6,"description":753,"image":760,"date":751,"topic":777,"genre":755,"shelf":775,"authors":788},[789],{"name":9},{"path":783,"title":791,"description":792,"image":793,"date":794,"topic":777,"genre":755,"shelf":775,"authors":795},"如何委派任务:让交接真正落地——任务简报、负责人、截止日期,以及双方都能查阅的记录(2026)","委派任务时,应交付一个成果,而不是一串步骤清单:一份一段话的任务简报,写明预期成果、截止日期和限制条件;一位明确口头应下任务的负责人;在工作开始前就约定好的检查节点;以及保存在双方日后都能查阅之处的交接记录。本文按步骤讲解这一方法,提供可直接复制的任务简报模板,介绍适用于多人参与工作的 RACI 图表,说明哪些事该委派、哪些该自己保留,以及交接记录在 Teams、Zoom、Google Workspace 和 Slack 中应存放在哪里,并说明任务完成与否如何在下一份会议回顾中以每位成员各自的语言反馈回来。","\u002Fblog\u002Fhow-to-delegate-tasks.svg","2026-10-23",[796],{"name":9},{"path":798,"title":799,"description":800,"image":801,"date":802,"topic":777,"genre":755,"shelf":775,"authors":803},"\u002Fblog\u002Fremote-work-policy","远程办公政策：模板、章节、示例——以及政策所在的唯一渠道（2026）","远程办公政策是一套关于在办公室之外工作的书面规则：谁可以远程办公、在哪里办公、何时必须保持联系畅通、团队如何沟通、谁来承担设备和网络费用、如何保障公司数据安全，以及政策本身如何审查。本文介绍一份可用的政策应包含的十个章节、一份可直接复制的模板、一份适用于分布在三个国家、共四十人的公司的完整示例、政策及其审查在 Teams、Zoom、Google Workspace 和 Slack 中的存放位置，以及如何通过一个渠道，让每位成员都能用自己的语言阅读政策、与之相关的每个问题和每一次变更。","\u002Fblog\u002Fremote-work-policy.svg","2026-10-22",[804],{"name":9},{"path":806,"title":807,"description":808,"image":809,"date":810,"topic":777,"genre":755,"shelf":775,"authors":811},"\u002Fblog\u002Fhow-to-improve-team-productivity","如何提升团队生产力:减少会议、书面状态更新,以及每个办公室都能阅读的历史记录(2026)","要提升团队生产力,只保留真正需要做出决定的会议,将状态同步改为在固定时间前发布的书面更新,并保留一份所有成员日后都能查阅的决策与任务历史记录。本文介绍这三个杠杆及其背后的计算方式,提供可直接复制的每周状态模板和 30 天计划,说明书面状态更新与会议记录在 Teams、Zoom、Google Workspace 和 Slack 中的存放位置,以及频道如何让每位成员都能用自己的语言阅读状态、任务和每一份会议回顾。","\u002Fblog\u002Fhow-to-improve-team-productivity.svg","2026-10-21",[812],{"name":9},{"path":61,"title":814,"description":815,"image":816,"date":817,"topic":777,"genre":755,"shelf":775,"authors":818},"SOP 模板:格式、示例、审查周期——以及每位成员都能用自己的语言阅读的 SOP(2026)","SOP 模板是标准操作规程的固定框架:包含编号、版本、负责人和审查日期的页眉,然后依次是目的、适用范围、角色、带有分工和预期结果的编号步骤、例外情况、记录、参考资料以及修订历史。本文介绍格式、可直接复制的模板、两个填写完整的示例、让规程始终保持准确的审查周期、SOP 及其审查在 Teams、Zoom、Google Workspace 和 Slack 中的存放位置,以及每位成员如何用自己的语言阅读规程及其每一次审查。","\u002Fblog\u002Fsop-template.svg","2026-10-20",[819],{"name":9},{"path":821,"title":822,"description":823,"image":824,"date":825,"topic":777,"genre":755,"shelf":775,"authors":826},"\u002Fblog\u002Fai-secretary","团队 AI 秘书:Mia 如今在会议、频道和日历中能做什么——以及当前工具的局限(2026)","AI 秘书是承担团队会议周边事务性工作的助手:它会准备会前简报、记录会议纪要、列出谁承诺了什么、把后续跟进事项放入日历,并在数周之后回答当时做出了哪些决定。本文介绍这项工作的具体内容、一份可直接复制用于交接的简报、Microsoft Teams、Zoom 和 Google Workspace 目前在这一主题下公开记载的功能,以及 InterMIND 的 Mia 在付费方案中能做什么——在会议中、在频道里,以及通过您已在使用的助手。","\u002Fblog\u002Fai-secretary.svg","2026-10-18",[827],{"name":9},{"path":829,"title":830,"description":831,"image":832,"date":833,"topic":777,"genre":755,"shelf":775,"authors":834},"\u002Fblog\u002Frecurring-meeting","周期性会议：如何在 Google Calendar 和 Outlook 中设置，以及如何将其历史记录集中保存（2026）","周期性会议是按固定规律（每周、每两周、每月）重复的单个日历事件，因此整个系列只需创建、邀请和修改一次，而无需逐次操作。本文介绍什么是周期性会议、什么是会议系列，每个周期性会议都需要的五项设置，如何在 Google Calendar 和 Outlook 中设置重复规则，以及如何只修改其中一次而不影响其余场次；提供一张可复制的系列卡片；说明每次会议的笔记和纪要在 Teams、Zoom、Google Workspace 和 Slack 中的存放位置；还介绍系列会议如何将所有场次集中在同一个频道中，并让每位成员都能以自己的语言阅读。","\u002Fblog\u002Frecurring-meeting.svg","2026-10-17",[835],{"name":9},{"path":468,"title":837,"description":838,"image":839,"date":840,"topic":777,"genre":755,"shelf":775,"authors":841},"决策日志模板:如何记录决策,避免重复争论——以及日志存放在哪里(2026)","决策日志是持续记录团队所作决策的台账,每项决策一条记录:用一句话概括的决策内容、决策人、被否决的方案及原因、该决策排除了什么、重新讨论该决策的触发条件,以及指向决策作出时刻的链接。本文介绍记录格式、可直接复制的模板和登记表、三条填写示例,日志在 Teams、Zoom、Google Workspace 和 Slack 中的存放位置,以及会议中作出的决策如何以一行内容回到会议纪要中,标注为已达成一致、待定或存在争议,并以每位成员各自的语言呈现。","\u002Fblog\u002Fdecision-log-template.svg","2026-10-16",[842],{"name":9},{"path":844,"title":845,"description":846,"image":847,"date":848,"topic":777,"genre":755,"shelf":775,"authors":849},"\u002Fblog\u002Fmeeting-cadence","会议节奏：每类会议应多久召开一次，附适用于 5 至 50 人团队的模板——以及每个周期性会议的历史记录保存在哪里（2026）","会议节奏是周期性会议的固定节律——多久召开一次、在哪一天和哪个时间、持续多长时间——按每个会议系列设定一次，而非按团队设定：每日会议用于处理阻塞问题，每周会议用于决策，每两周一次用于评审，每月或每季度一次用于确定方向。本文介绍选择会议节奏的四条规则、大多数团队所运行各类会议的节奏、适用于 5 人、15 人和 50 人团队的模板及其所耗费的工时、提示应调整节奏的信号——以及每个周期性会议的历史记录在 Teams、Zoom、Google Workspace 和 Slack 中的保存位置，还有在一个能以每位成员的语言保留每场会议内容的频道中的保存方式。","\u002Fblog\u002Fmeeting-cadence.svg","2026-10-15",[850],{"name":9},{"path":852,"title":853,"description":854,"image":855,"date":856,"topic":777,"genre":755,"shelf":775,"authors":857},"\u002Fblog\u002Fhow-to-run-an-effective-meeting","如何召开高效会议:会前、会中、会后——以及留存会议决议的渠道(2026)","要召开高效会议,请用一句话确定会议目的,提前一天发送议程清单,按时间盒推进议程并为每个议项指定负责人,在最后五分钟复述每项决议和行动事项,并在当天发布会议纪要。本文介绍三个阶段各自的实操要点、可直接复制的会议流程表,说明会议记录在 Teams、Zoom、Google Workspace 和 Slack 中的存放位置,以及在频道中召开的会议如何让每位成员都能用自己的语言阅读议程、聊天记录和会议纪要。","\u002Fblog\u002Fhow-to-run-an-effective-meeting.svg","2026-10-14",[858],{"name":9},{"path":860,"title":861,"description":862,"image":863,"date":864,"topic":777,"genre":755,"shelf":775,"authors":865},"\u002Fblog\u002Fproject-kickoff-meeting","启动会议(Kick off meeting):议程、清单、示例——适用于项目和新客户,以及启动会议如何成为项目频道(2026)","启动会议是项目的第一次会议,由将要执行工作的人员在任何工作开始之前,共同明确项目的目的、“完成”的定义、各部分的负责人、沟通方式以及可能出现的风险。本文涵盖:启动会议必须留下的成果;会前、会中、会后清单;可直接复制的 60 分钟议程;内部项目和新客户各一份已填写的示例;会议记录在 Teams、Zoom、Google Workspace 和 Slack 中的存放位置;以及启动会议如何成为项目后续所有会议所在的频道,让每位成员都能用自己的语言阅读。","\u002Fblog\u002Fproject-kickoff-meeting.svg","2026-10-12",[866],{"name":9},{"path":868,"title":869,"description":870,"image":871,"date":872,"topic":873,"genre":755,"shelf":756,"authors":874},"\u002Fblog\u002Fenglish-gets-the-first-contact","英语只是初次接触，交易则以合作伙伴的语言进行","出口交易中，英语在哪个环节止步，按阶段逐一梳理：询价、报价、谈判、索赔、续订。出口部门目前为合作伙伴的语言支付多少费用，附价格与来源，以及交易结束后还会留下什么。","\u002Fblog\u002Fenglish-gets-the-first-contact.svg","2026-10-11","live-translation",[875],{"name":9},{"path":877,"title":878,"description":879,"image":880,"date":872,"topic":777,"genre":755,"shelf":775,"authors":881},"\u002Fblog\u002Fstand-up-meeting","站立会议：形式、每日议程、异步变体——以及两次站会之间频道做了什么（2026）","站立会议是一个团队每天举行的简短会议——最长十五分钟，每个工作日同一时间——每个人依次说明自昨天以来完成了什么、到明天为止将做什么，以及有什么在阻碍自己，让阻碍在解决成本还很低时就浮出水面。本文介绍站立会议的形式及其六条规则、三个经典问题以及效果更好的替代版本、可直接复制的每日议程、适用于跨时区团队的异步变体，以及您已在使用的工具如何在两次站会之间处理这些阻碍。","\u002Fblog\u002Fstand-up-meeting.svg",[882],{"name":9},{"path":884,"title":885,"description":886,"image":887,"date":888,"topic":777,"genre":755,"shelf":775,"authors":889},"\u002Fblog\u002Fall-hands-meeting","全员会议：议程、形式、示例——以及各地办公室如何用自己的语言收听（2026）","全员会议是全公司共同参加的一场会议——管理层分享数据、决策和故事，每个人都可以就此提问。本文介绍行之有效的会议形式、按公司规模划分的召开频率、可直接复制的议程模板、三个填写完整的示例、全员会议在 Teams、Zoom、Google Workspace 和 Slack 中的位置，以及会后提问、回答和决策如何同步给早上 7 点加入的办公室和晚上 9 点加入的办公室。","\u002Fblog\u002Fall-hands-meeting.svg","2026-10-10",[890],{"name":9},{"path":892,"title":893,"description":894,"image":895,"date":896,"topic":777,"genre":755,"shelf":775,"authors":897},"\u002Fblog\u002Faction-items","Action items:如何撰写、分配和跟踪(以及会议纪要如何保留清单)(2026)","Action item 是会议产生的一项任务,以动词开头,明确一位负责人和一个截止日期,让没有参会的人也能看明白将会发生什么、由谁来推动落实。本文介绍其格式、如何在会议进行中和结束时撰写事项、如何分配才能真正完成,并提供可直接复制的模板和跟踪表,以及 Action item 在 Teams、Zoom、Google Workspace 和 Slack 中的存放位置,还有定期会议的纪要如何生成清单、在下一次会议上回顾清单,并将每一项标记为已完成或未完成。","\u002Fblog\u002Faction-items.svg","2026-10-09",[898],{"name":9},{"path":900,"title":901,"description":902,"image":903,"date":904,"topic":777,"genre":755,"shelf":775,"authors":905},"\u002Fblog\u002Fmeeting-notes-template","会议记录模板:记录哪些内容、现在由谁来写,以及通话结束后记录存放在哪里(2026)","会议记录模板是一份供您在通话期间填写的单页版式:会议目的与出席人员;每个议题一个区块,记录讨论内容、已做出的决定,以及谁在何时前完成什么;另设“待议事项”区,收纳已提出但尚未解决的内容。本文介绍其格式、可直接复制的模板、两个已填写的示例、会议记录与会议纪要及会后总结的区别,以及记录在 Teams、Zoom、Google Workspace 和 Slack 中的存放位置,还有通话结束后这些记录会如何处理。","\u002Fblog\u002Fmeeting-notes-template.svg","2026-10-08",[906],{"name":9},{"path":908,"title":909,"description":910,"image":911,"date":912,"topic":913,"genre":914,"shelf":756,"authors":915},"\u002Fblog\u002Ftranslated-captions-and-live-translation-in-the-room","会议期间的翻译字幕、实时翻译与 AI 助手:每位参与者如何在 InterMIND 会议室内使用(2026)","新一类会议助手以浏览器标签页的形式与通话并行运行,为单个用户提供其所用语言的实时转录、翻译,并在对话进行时提供 AI 辅助。本文介绍在 InterMIND 中如何于会议室内完成同样的工作:由主持人为所有人提供该功能,每位参与者以自己的语言阅读和收听,会后转录和会议纪要仍然保留,同时也如实说明其局限所在。","\u002Fblog\u002Ftranslated-captions-and-live-translation-in-the-room.svg","2026-10-06","video-meetings","editorial",[916],{"name":9},{"path":918,"title":919,"description":920,"image":921,"date":922,"topic":777,"genre":755,"shelf":775,"authors":923},"\u002Fblog\u002Fmeeting-agenda-examples","12 种会议的会议议程示例——以及每场会议留下的成果(2026)","十二个可直接复制的会议议程示例——每周团队会议、每日站会、一对一沟通、项目启动会、迭代评审会、复盘会、全员大会、领导层会议、采用一致同意议程的董事会会议、客户电话会议、客户 QBR 和招聘复盘会——每个示例都包含目的、议程项、负责人和会议纪要,并补充了大多数示例所忽略的一点:会议会留下什么,以及以谁的语言留下。","\u002Fblog\u002Fmeeting-agenda-examples.svg","2026-10-04",[924],{"name":9},{"path":926,"title":927,"description":928,"image":929,"date":922,"topic":777,"genre":755,"shelf":775,"authors":930},"\u002Fblog\u002Fmeeting-agenda-template","会议议程模板:格式、示例,以及议程如何转化为会议纪要(2026)","会议议程是对会议目的的清单:列出各项议题,按顺序排列,并为每项明确负责人、时间限制以及所需达成的结果。本文介绍议程的格式、可直接复制的模板、针对大多数团队实际召开的会议所提供的五个填写示例、议程在 Microsoft Teams、Zoom、Google Calendar、Google Docs 和 Slack 中的存放位置,以及通话结束后每个议题如何以已决定、未解决或已推迟的状态,用每位参会者各自的语言回到会议纪要中。","\u002Fblog\u002Fmeeting-agenda-template.svg",[931],{"name":9},{"path":933,"title":934,"description":935,"image":936,"date":922,"topic":777,"genre":755,"shelf":775,"authors":937},"\u002Fblog\u002Fone-on-one-meeting-template","一对一会议模板:结构、节奏,以及双方都能查阅的持续记录(2026)","一对一会议是下属的会议,而不是经理的状态汇报。本文介绍 30 分钟模板和 45 分钟月度版本,如何准备和主持会议,多久举行一次,与新下属的首次一对一会议,按情境整理的十五个问题,以及一对一会议的持续记录应存放在何处:Teams、Slack,还是让双方都能以各自语言阅读的专属空间。","\u002Fblog\u002Fone-on-one-meeting-template.svg",[938],{"name":9},{"path":940,"title":941,"description":942,"image":943,"date":944,"topic":913,"genre":914,"shelf":756,"authors":945},"\u002Fblog\u002Ftranslation-captions-and-transcript-in-one-meeting","实时翻译、字幕和可搜索的转录文本如何在一场 InterMIND 会议中协同工作","语音翻译、实时字幕和可搜索的转录文本,正越来越多地作为一个整体打包出现在各类会议和协作平台的宣传中。但这个组合的实际含义因厂商而异:大多数产品页面只是列出这三项功能,却没有说明每项功能的具体表现,例如需要由谁来开启、访客能获得什么,或者“可搜索”究竟涵盖哪些内容。本文将具体说明在 InterMIND 会议中这三项功能各自如何运作、哪些功能默认开启,以及它们真实存在的局限。","\u002Fblog\u002Ftranslation-captions-and-transcript-in-one-meeting.svg","2026-09-23",[946],{"name":9},{"path":948,"title":949,"description":950,"image":951,"date":952,"topic":953,"genre":914,"shelf":756,"authors":954},"\u002Fblog\u002Fintermind-for-slack-how-it-works","InterMIND for Slack 工作原理:用 \u002Fintermind 发起会议,会议纪要自动回到对话串中(2026)","InterMIND 的 Slack 应用只新增一个斜杠命令。\u002Fintermind 可在您当前所在的频道中发起会议(立即开始,或在您指定的时间开始),并发布加入链接;会议结束后,会议回顾会作为回复回到同一条对话串中,或发送到您通过 \u002Fintermind recaps here 指定的频道。粘贴的会议链接会自动展开为卡片。该应用仅申请五项权限,不会读取您的任何消息。本文介绍安装、账户连接和会议回顾投递的工作方式,以及相关限制。","\u002Fblog\u002Fintermind-for-slack-how-it-works.svg","2026-09-17","integrations",[955],{"name":9},{"path":957,"title":958,"description":959,"image":960,"date":961,"topic":962,"genre":914,"shelf":756,"authors":963},"\u002Fblog\u002Fpay-only-for-active-members","只为实际使用的成员付费:InterMIND 改为按活跃成员计费","Pro 和 Business 不再销售需要手动分配的席位。您可以邀请整个团队;每次续订时,系统会统计过去 28 天内活跃的成员,并仅按这一人数计费。长期未活动的成员保留访问权限,且不产生任何费用;会议访客和外部频道参与者始终免费。本文介绍如何界定“活跃”、计费周期内人数如何变化、续订前通知函的内容,以及您的账单页面将发生哪些变化。","\u002Fblog\u002Fpay-only-for-active-members.svg","2026-09-16","whats-new",[964],{"name":9},{"path":966,"title":967,"description":968,"image":969,"date":961,"topic":970,"genre":914,"shelf":756,"authors":971},"\u002Fblog\u002Fspeech-to-text-on-your-own-gateway","Azure AI Speech、Google Chirp 3 与 Amazon Transcribe 在 153 条语音备忘录上的对比:InterMIND 为何在贵组织自有的云网关上运行语音转文字(2026)","我们在同一套测试框架下、于同一天,使用 17 种语言的 153 条语音备忘录音频片段,对 InterMIND 组织可选的三种云网关所提供的语音转文字服务——Azure AI Speech、Google Cloud Speech-to-Text(Chirp 3)和 Amazon Transcribe——进行了测评。内容包括各语言的词错误率、测试方法、各 API 的局限性,以及为什么识别器应当跟随网关,而不是跟随排行榜。","\u002Fblog\u002Fspeech-to-text-on-your-own-gateway.svg","it-admin",[972],{"name":9},{"path":974,"title":975,"description":976,"image":977,"date":978,"topic":953,"genre":755,"shelf":756,"authors":979},"\u002Fblog\u002Fai-meeting-assistant-in-the-meeting","在会议中主动行动的 AI 会议助手:Teams Facilitator、Zoom AI Companion、Google Meet Gemini 与 InterMIND 在会议现场做什么(2026)","AI 记录工具在通话结束后撰写纪要,而 AI 会议助手在会议进行中就开始工作:提醒与会者上次的决定,在承诺被说出的那一刻就记录下来,在主持人提出要求时安排后续会议,并在会议结束前提出下一步建议。本文依据各厂商的官方文档,介绍 Microsoft Teams(Facilitator)、Zoom(AI Companion、ZoomMate)、Google Meet(Ask Gemini、后续步骤)和 InterMIND(Mia)中的具体表现,并附有与 AI 参与者共同开会的操作指南。","\u002Fblog\u002Fai-meeting-assistant-in-the-meeting.svg","2026-09-11",[980],{"name":9},{"path":982,"title":983,"description":984,"image":985,"date":978,"topic":953,"genre":914,"shelf":756,"authors":986},"\u002Fblog\u002Fconnect-your-ai-assistant-to-intermind","在您常用的助手中管理会议:将 InterMIND 连接到 Claude、ChatGPT、Copilot 或 Gemini(MCP 连接器)","InterMIND 的 MCP 连接器现已为您的 AI 助手提供十种工具:创建或安排会议、查看会议纪要和转写文本、搜索已做出的决定、在您的频道中阅读和发布消息、列出共享文档。本文介绍可以向助手提出哪些请求、如何连接各个助手,以及该连接器无法实现的功能。","\u002Fblog\u002Fconnect-your-ai-assistant-to-intermind.svg",[987],{"name":9},{"path":989,"title":990,"description":991,"image":992,"date":993,"topic":994,"genre":914,"shelf":756,"authors":995},"\u002Fblog\u002Fhow-to-add-an-external-client-to-a-team-chat-channel","如何通过电子邮件将外部客户或合作伙伴添加到团队聊天频道——对方无需已有账号(2026)","让客户留在您的频道里,而不是淹没在收件箱中。在 InterMIND 中,您可以在成员抽屉中通过电子邮件地址将外部人员添加到频道:已注册用户会立即加入,其他人会收到电子邮件邀请,并在注册后加入;您在会议中已经见过的人会被标记为“已会面”。此后,他们可以用自己的语言阅读整个频道的内容——每条消息、每个文件、每份会议纪要——并且可以加入该频道发起的每一场通话。本文介绍谁可以添加成员、外部成员能看到什么、邀请链接及其轮换方法,以及这与单场会议的访客有何不同。","\u002Fblog\u002Fhow-to-add-an-external-client-to-a-team-chat-channel.svg","2026-09-10","team-chat",[996],{"name":9},{"path":998,"title":999,"description":1000,"image":1001,"date":993,"topic":913,"genre":914,"shelf":756,"authors":1002},"\u002Fblog\u002Fhow-to-check-network-and-devices-during-a-video-call","如何在视频通话中检查网络并切换摄像头、麦克风或扬声器——无需退出通话(2026)","当通话听起来不对劲时,首先要弄清问题出在哪一方。在 InterMIND 中,每位参与者(而不仅仅是主持人)都可以从会议设置的“设备”部分打开网络统计信息,从设备子菜单中切换摄像头、麦克风和扬声器,而不会中断音频或视频;在下一次通话之前,还可以使用测试房间进行检测,无需账号,也无需链接。本文介绍各项控制所在的位置、统计信息显示的内容、通话过程中设备被拔出时会发生什么,以及哪些设置在会话结束后仍会保留。","\u002Fblog\u002Fhow-to-check-network-and-devices-during-a-video-call.svg",[1003],{"name":9},{"path":1005,"title":1006,"description":1007,"image":1008,"date":993,"topic":994,"genre":914,"shelf":756,"authors":1009},"\u002Fblog\u002Fhow-to-forward-select-and-delete-messages-in-a-team-chat","如何在团队聊天中转发、选择和批量删除消息，并通过键盘浏览历史记录（2026）","在 InterMIND 中，团队聊天的日常整理只需四步：将一条消息或整个讨论串转发到其他频道或您的收件箱（通过菜单，或将其拖到频道上）；在空白处拖动以选择多条消息；经一次确认后删除所选内容；即使在输入时，也可使用 PageUp、PageDown、Home 和 End 翻阅历史记录。本文说明转发时会带上哪些内容、哪些内容不会带上，谁可以删除哪些消息，为什么转发会先作为草稿暂存而不是直接发送，并引用 Slack 和 Microsoft Teams 官方文档中关于转发消息的说明。","\u002Fblog\u002Fhow-to-forward-select-and-delete-messages-in-a-team-chat.svg",[1010],{"name":9},{"path":1012,"title":1013,"description":1014,"image":1015,"date":993,"topic":953,"genre":914,"shelf":756,"authors":1016},"\u002Fblog\u002Fhow-to-get-a-copy-of-every-meeting-recap-in-your-crm-by-email","2026 年如何通过电子邮件将每场会议纪要的副本发送到您的 CRM 或服务台——无需集成,只需一个已确认的地址","每个 CRM、服务台和问题跟踪工具都有一个入站邮箱地址,可将邮件转换为备注或工单。在 InterMIND 中,主持人将该地址添加为会议或频道的纪要副本收件人,通过一封测试邮件确认一次后,该会议室的每份纪要都会以隐藏密送(BCC)的方式发送到该地址——内容与参会者收到的摘要相同,并附有完整纪要和转录文本的链接。本文介绍:在哪里设置、一小时的确认有效期、最多可保存十个地址的地址簿、副本包含的内容、谁可以打开这些链接,以及何时改用 Zapier 或 API。","\u002Fblog\u002Fhow-to-get-a-copy-of-every-meeting-recap-in-your-crm-by-email.svg",[1017],{"name":9},{"path":1019,"title":1020,"description":1021,"image":1022,"date":993,"topic":994,"genre":914,"shelf":756,"authors":1023},"\u002Fblog\u002Fhow-to-get-a-summary-of-every-document-shared-in-a-team-chat","如何自动获取团队聊天中每份共享文档的摘要——使用您的语言,并附带来源链接(2026)","发送到 InterMIND 频道或会议聊天中的每份文档都会被单独生成摘要,无需点击任何按钮。文件上传几秒后,其卡片上就会显示 AI 摘要:以简短要点列出关键内容,每条要点末尾都带有 ¶ 链接,可直接跳转到其来源的具体段落,每位成员都能以自己的语言阅读。本文介绍支持哪些格式、为什么提取的文本不会被翻译、无法生成摘要时卡片会显示什么、文本在何处处理以及谁可以阅读,还有这些摘要如何汇入会议纪要。","\u002Fblog\u002Fhow-to-get-a-summary-of-every-document-shared-in-a-team-chat.svg",[1024],{"name":9},{"path":1026,"title":1027,"description":1028,"image":1029,"date":993,"topic":913,"genre":914,"shelf":756,"authors":1030},"\u002Fblog\u002Fhow-to-hand-over-a-meeting-or-channel-to-another-host","如何将会议或频道移交给其他主持人——通话中或有人离开公司时(2026)","InterMIND 会议或频道的主持人,是会议室计费所属的对象,同时负责准许访客加入、管理成员以及为所有人结束通话。通过“设为主持人”,您只需一键即可将该角色移交给同事——在进行中的通话里,新主持人会立即获得主持权限;如果原主持人已离职,团队管理员也可以代为操作。本文说明谁可以移交给谁、为什么新主持人必须是同一团队中使用付费方案的已授权成员、对参会者有哪些变化和哪些保持不变,以及变更记录在何处。","\u002Fblog\u002Fhow-to-hand-over-a-meeting-or-channel-to-another-host.svg",[1031],{"name":9},{"path":1033,"title":1034,"description":1035,"image":1036,"date":993,"topic":913,"genre":914,"shelf":756,"authors":1037},"\u002Fblog\u002Fhow-to-join-a-video-meeting-from-your-computer","如何通过电脑加入视频会议:链接、摄像头和麦克风、您的语言——有账号或无账号均可(2026)","加入 InterMIND 会议只需在浏览器中完成三步——支持 Chrome、Edge 或 Firefox,无需安装任何软件。点击链接;已登录时,您将进入加入前的预览界面;未登录时,输入您的姓名,以访客身份加入,并等待主持人放行。预览摄像头,选择麦克风和扬声器,然后在“更多”中选择您的翻译语言:您将以自己的语言听到每位参会者的发言,且保留其本人的声音,字幕一键即可开启。访客可以使用哪些功能、哪些功能需要账号、五分钟规则、故障排查表——以及引用 Google Meet 和 Microsoft Teams 官方文档,说明二者如何让没有账号的参会者加入会议。","\u002Fblog\u002Fhow-to-join-a-video-meeting-from-your-computer.svg",[1038],{"name":9},{"path":1040,"title":1041,"description":1042,"image":1043,"date":993,"topic":913,"genre":914,"shelf":756,"authors":1044},"\u002Fblog\u002Fhow-to-present-to-everyone-and-scroll-your-shared-tab-without-leaving-the-call","如何在视频会议中向所有人演示——无需离开通话即可滚动共享的标签页(2026)","共享屏幕通常做不到的两件事。在 InterMIND 中,“向所有人演示”会把您主舞台上的共享内容——屏幕、文档或回顾摘要——同时呈现在每位参会者的主舞台上,中途加入的人也会直接看到。而当您共享浏览器标签页时,在自己的共享预览上滚动鼠标滚轮即可滚动该标签页,无需切换窗口向下翻页。本文介绍这两项功能的工作方式、滚动功能所需的一项浏览器权限、观看者保留的操作权限,以及会议结束后留存的内容。","\u002Fblog\u002Fhow-to-present-to-everyone-and-scroll-your-shared-tab-without-leaving-the-call.svg",[1045],{"name":9},{"path":1047,"title":1048,"description":1049,"image":1050,"date":993,"topic":913,"genre":914,"shelf":756,"authors":1051},"\u002Fblog\u002Fhow-to-run-an-audio-only-call-in-a-video-meeting","如何在视频会议中进行纯音频通话:语音舞台、一个可复制的链接,以及会后回顾(2026)","并非每次通话都需要一整面的人脸画面。在 InterMIND 中,您只需将所有画面移到侧边栏,舞台就会清空并变成语音舞台:一个安静的面板,提供快捷操作和“复制链接”按钮,而会议室依然完全保持活跃——每个人都能以自己的语言听到彼此,聊天保持开启,挂断后即可收到会后回顾。本文介绍如何用一个按键切换进出该模式、空舞台提供哪些功能、翻译音频通话与翻译视频通话有何不同,以及手机应用如何让通话在切换到其他应用时依然保持不中断。","\u002Fblog\u002Fhow-to-run-an-audio-only-call-in-a-video-meeting.svg",[1052],{"name":9},{"path":1054,"title":1055,"description":1056,"image":1057,"date":993,"topic":913,"genre":914,"shelf":756,"authors":1058},"\u002Fblog\u002Fhow-to-schedule-a-meeting-from-google-calendar-or-outlook","如何通过 Google Calendar 或 Outlook 安排会议:一键完成,链接已在其中(2026)","只需在“集成”中连接一次 Google Calendar 或 Outlook。此后,“新建会议”按钮的日历部分会创建会议室但不进入,并打开已预填活动信息的日历,包括标题、加入链接和会议回顾链接。添加参会人员,选择日期;若是例行会议,再设置重复规则,每位参会者都会在邀请中收到该链接。该链接是永久有效的,因此同一个会议室会逐周保留其聊天记录和每一份会议回顾;在日历中更改日期,会议记录行也会随之移动。本文介绍其工作方式、团队之外的访客如何处理该邀请,并引用官方文档,说明 Google Meet 和 Microsoft Teams 是如何安排同样的会议的。","\u002Fblog\u002Fhow-to-schedule-a-meeting-from-google-calendar-or-outlook.svg",[1059],{"name":9},{"path":1061,"title":1062,"description":1063,"image":1064,"date":993,"topic":970,"genre":914,"shelf":756,"authors":1065},"\u002Fblog\u002Fhow-to-see-who-uses-your-translation-minutes-and-storage","如何查看谁在使用您的翻译分钟数和存储空间,并在达到上限前收到电子邮件提醒(2026)","InterMIND 的每项额度均按会议主持人计量:您创建的会议中的语音翻译分钟数、为参会者提供的聊天翻译字数、已翻译的文档数量,以及团队共享的存储空间。账单页面以滚动 30 天为周期显示每项计量,当您接近存储上限或首次达到翻译分钟数上限时,系统会发送电子邮件。本文介绍每项计量统计的内容、达到上限后会发生什么(会议继续进行,翻译暂停),以及 30 天周期如何自动恢复额度。","\u002Fblog\u002Fhow-to-see-who-uses-your-translation-minutes-and-storage.svg",[1066],{"name":9},{"path":1068,"title":1069,"description":1070,"image":1071,"date":993,"topic":953,"genre":914,"shelf":756,"authors":1072},"\u002Fblog\u002Fhow-to-send-meeting-recaps-to-your-crm-with-zapier-or-the-api","如何将会议纪要发送到您的 CRM、帮助台或电子表格:Zapier、webhook 或 API(2026)","InterMIND 生成的每份会议纪要,都可以直接进入您日常工作的工具,无需任何人手动复制。三种接入方式:使用 Meeting Recap Ready 触发器和 Create Meeting Link 操作的 Zapier;使用 HMAC 签名的 recap.ready webhook;或使用个人密钥、三个端点,以及面向 Make、n8n、Pipedream 和 AI 智能体的 OpenAPI 契约的 API。本文还介绍了负载包含哪些内容、投递规则和各项限制,以及完全无需集成的一种方式:将入站电子邮件地址设为会议纪要副本收件人。","\u002Fblog\u002Fhow-to-send-meeting-recaps-to-your-crm-with-zapier-or-the-api.svg",[1073],{"name":9},{"path":1075,"title":1076,"description":1077,"image":1078,"date":993,"topic":994,"genre":914,"shelf":756,"authors":1079},"\u002Fblog\u002Fhow-to-share-a-file-into-your-team-chat-from-any-app","如何在 iPhone、Android 或 Mac 上从任意应用将文件、照片或链接分享到团队聊天(2026)","InterMIND 位于您手机的分享面板和 Mac 的“共享”菜单中。在任意应用中选择它——无论是照片、PDF、链接还是一段文字——然后选择发送位置:您自己的收件箱或某个频道。每个文件最大 25 MB,将以消息形式送达;文档会自动生成摘要,频道中的每位成员都能以自己的语言阅读文本。本文介绍各平台提供的功能、收件箱的来源、桌面端和浏览器端的替代方式,以及哪些内容会占用存储空间。","\u002Fblog\u002Fhow-to-share-a-file-into-your-team-chat-from-any-app.svg",[1080],{"name":9},{"path":1082,"title":1083,"description":1084,"image":1085,"date":993,"topic":913,"genre":914,"shelf":756,"authors":1086},"\u002Fblog\u002Fhow-to-share-your-phone-screen-in-a-video-meeting","如何在视频会议中从 iPhone 或 Android 共享手机屏幕(2026)","在 InterMIND 的 iOS 和 Android 应用中,共享手机屏幕的方式与笔记本电脑共享显示器类似:在应用中开始共享,授予系统的屏幕捕获权限,会议室中的其他人便会将您的手机画面视为主显示。在接收端,可以通过双指缩放来放大共享屏幕,并将其旋转为横屏;他人在笔记本电脑上绘制的激光笔标记,也会出现在您手机上的相同位置。本文介绍手机在共享中能做什么、不能做什么,通话结束后会保留哪些内容,并引用 Google Meet 和 Microsoft Teams 的官方文档,说明它们对从手机应用共享屏幕的相关规定。","\u002Fblog\u002Fhow-to-share-your-phone-screen-in-a-video-meeting.svg",[1087],{"name":9},{"path":1089,"title":1090,"description":1091,"image":1092,"date":993,"topic":913,"genre":914,"shelf":756,"authors":1093},"\u002Fblog\u002Fhow-to-share-your-screen-in-a-video-meeting","如何在视频会议中共享屏幕:整个屏幕、窗口或标签页、手机端共享、激光笔(2026)","在 InterMIND 中共享屏幕只需一次点击和一个选择:整个屏幕、某个窗口,或是可同时共享音频的浏览器标签页。所有人都会将其视为主显示画面,激光笔在每台设备上都会落在同一位置,iOS 和 Android 应用也能以同样方式共享手机屏幕。本文还涵盖演示者模式、多位演示者同时共享、谁有权限共享、通话结束后会留下什么,并引用官方文档,说明 Google Meet 和 Microsoft Teams 的共享功能在哪些方面存在限制。","\u002Fblog\u002Fhow-to-share-your-screen-in-a-video-meeting.svg",[1094],{"name":9},{"path":1096,"title":1097,"description":1098,"image":1099,"date":993,"topic":994,"genre":914,"shelf":756,"authors":1100},"\u002Fblog\u002Fhow-to-start-a-call-from-a-team-chat","如何从团队聊天发起通话:一键加入,聊天内容随您同行,会议回顾自动回传(2026)","每个 InterMIND 频道都有专属的会议室。点击聊天顶部的“加入”,在加入前的页面中设置摄像头和麦克风,即可进入会议——团队成员以同样方式加入,无需审批。频道聊天会保留在会议侧边栏中;挂断后,会议回顾会自动发布回频道,让讨论从通话结束的地方继续。本文介绍其工作方式、谁可以加入、哪些内容会保留,并引用 Slack 和 Teams 官方文档,说明 Slack huddle 与 Teams 聊天通话在同一任务上的处理方式。","\u002Fblog\u002Fhow-to-start-a-call-from-a-team-chat.svg",[1101],{"name":9},{"path":1103,"title":1104,"description":1105,"image":1106,"date":1107,"topic":953,"genre":914,"shelf":756,"authors":1108},"\u002Fblog\u002Fmcp-servers-for-meeting-tools","2026 年最佳会议 MCP 服务器：Zoom、Teams、Fireflies、Otter、Granola 和 InterMIND 向您的 AI 助手开放了哪些能力","MCP 服务器可以把会议工具变成 AI 助手能够直接调用的能力，您无需离开已经打开的聊天窗口，例如 Claude、ChatGPT、Copilot、Gemini、Cursor。本指南对比了各厂商文档中公开的信息：AI 助手是只能读取转录文本，还是也能执行操作；需要哪种方案才能启用；如何登录；以及服务器在哪里上架。涵盖 Zoom、Microsoft 365 \u002F Teams、Google Meet、Fireflies、Otter、Granola、tl;dv、Fathom、Read AI 和 InterMIND，均依据其自身文档整理。","\u002Fblog\u002Fmcp-servers-for-meeting-tools.svg","2026-09-09",[1109],{"name":9},{"path":1111,"title":1112,"description":1113,"image":1114,"date":1107,"topic":970,"genre":914,"shelf":756,"authors":1115},"\u002Fblog\u002Fmeeting-ai-on-your-own-cloud-gateway","在您已在使用的 AI 云上生成会议纪要:主持人如何为整个组织一次性选定 Azure、Google 或 AWS","如今每款会议工具都内置了 AI,而每项 AI 功能都会增加一个子处理方。本文介绍 InterMIND 如何在您的组织已在使用的超大规模云服务商网关上运行其 AI 功能——欧盟数据区内的 Azure OpenAI、欧盟地区的 Google Vertex AI、您自己 AWS 账户中的 Amazon Bedrock——并提供按组织设置的关闭开关,以及主持人可验证的内容。","\u002Fblog\u002Fmeeting-ai-on-your-own-cloud-gateway.svg",[1116],{"name":9},{"path":1118,"title":1119,"description":1120,"image":1121,"date":1107,"topic":913,"genre":914,"shelf":756,"authors":1122},"\u002Fblog\u002Fteams-meeting-shared-files","Teams 会议共享文件:官方文档的说明,以及共享文件如何在会议中变成答案","Microsoft 于 2026 年 9 月 8 日将“会议共享文件”(Meeting Shared Files)加入 Microsoft 365 路线图——附加到会议的文件和链接会与所有参会者共享,并由会议中的 AI 用作回答依据。该路线图条目标记为 Teams 和 Microsoft Copilot;Microsoft 自己的文档指出,使用 Facilitator 需要 Copilot 许可证,它仅适用于已安排的会议,并且外部参会者看不到其实时更新。本文梳理了该功能的文档说明,并对照 InterMIND 中同一任务的实现方式:文件进入会议后,其摘要会自动出现,Mia 会以语音回答与该文件相关的问题,每位参会者都能听到她使用自己的语言作答。","\u002Fblog\u002Fteams-meeting-shared-files.svg",[1123],{"name":9},{"path":1125,"title":1126,"description":1127,"image":1128,"date":1129,"topic":777,"genre":914,"shelf":756,"authors":1130},"\u002Fblog\u002Fkeep-meeting-transcript-summary-after-the-call","Microsoft Teams 和 Google Meet 将您的转录文本、录制内容和摘要存储在哪里——以及如何在通话结束后保存它们","想知道 Teams 把转录文本保存在哪里？它并不在录制文件旁边。在 Microsoft Teams 和 Google Meet 中，录制内容、转录文本和 AI 摘要是三个独立的对象，存放在三个不同的位置，各自拥有三份权限列表，移动其中一个并不会同时移动其他对象——Microsoft 自己的文档也指出，Teams 录制文件被移动后，字幕将无法得到完全支持。本文提供一份有据可查的图谱，说明每种产物存放在何处、之后谁仍然可以打开它，以及当会议是一个“空间”而不是一个文件夹里的若干文件时会是什么样子。","\u002Fblog\u002Fkeep-meeting-transcript-summary-after-the-call.svg","2026-09-05",[1131],{"name":9},{"path":1133,"title":1134,"description":1135,"image":1136,"date":1129,"topic":994,"genre":914,"shelf":756,"authors":1137},"\u002Fblog\u002Fvoice-notes-in-a-team-channel","团队频道中的语音备忘:工作原理,以及 Copilot、Slack 和 Teams 如何处理录制的消息","在任意 InterMIND 频道中录制语音备忘,它会以文字消息的形式送达——即自动生成的转写文本,每位成员都能以自己的语言阅读——录音只需轻点一下即可播放。本文介绍其运作机制与限制,并将其与 Copilot Record、Slack clips 和 Teams clips 进行有据可查的对比:录音存放在哪里、时长上限是多少、是否自动生成转写文本,以及谁可以阅读。","\u002Fblog\u002Fvoice-notes-in-a-team-channel.svg",[1138],{"name":9},{"path":1140,"title":1141,"description":1142,"image":1143,"date":1144,"topic":994,"genre":914,"shelf":756,"authors":1145},"\u002Fblog\u002Femail-to-channel-no-bot","邮件转频道:任何服务无需机器人即可发帖到团队聊天——为什么邮件地址优于机器人令牌","每个 InterMIND 频道都有自己的专属邮件地址。将监控工具、工单系统、CRM 或 CI 流水线指向该地址,邮件就会出现在频道中供所有人查看,附件完整保留,每位成员都能以自己的语言阅读。完整机制说明:会送达哪些内容、会剥离哪些内容、有哪些限制,并与基于机器人的集成在设置、密钥、重试以及谁可以将其关闭等方面进行并排对比。","\u002Fblog\u002Femail-to-channel-no-bot.svg","2026-09-04",[1146],{"name":9},{"path":1148,"title":1149,"description":1150,"image":1151,"date":1152,"topic":777,"genre":755,"shelf":756,"authors":1153},"\u002Fblog\u002Fbook-a-demo","预约演示:如何用日历和一个会议链接搭建演示流程(2026)","本文介绍“预约演示”的含义,它与免费试用和探索性沟通电话有何不同,以及如何向供应商申请演示;同时介绍小型团队如何在没有 SDR 工具栈的情况下运行演示流程:在已有的日历中创建预约页面,在说明中放置一个可重复使用的会议链接,双方各用自己的语言交流,并让会后总结自动归档到 CRM。我们自己的“预约通话”页面就是实际示例。","\u002Fblog\u002Fbook-a-demo.svg","2026-09-02",[1154],{"name":9},{"path":1156,"title":1157,"description":1158,"image":1159,"date":1152,"topic":777,"genre":755,"shelf":756,"authors":1160},"\u002Fblog\u002Fdiscovery-call","探索电话（Discovery Call）：定义、执行方法，以及如何使用潜在客户的母语进行沟通（2026）","探索电话（Discovery Call）是与潜在客户的第一次正式沟通：您要了解对方的问题是否正是您能解决的，对方也会判断您是否值得再约一次会议。本文提供 30 分钟议程、15 个问题、一份简短的话术，以及通话后的后续步骤；同时为更愿意用自己思考时所用语言作答的潜在客户，提供三步设置方案：在日历中创建预约页面、使用一个可重复使用的会议链接，以及自动归档到 CRM 的会议纪要。","\u002Fblog\u002Fdiscovery-call.svg",[1161],{"name":9},{"path":1163,"title":1164,"description":1165,"image":1166,"date":1152,"topic":777,"genre":755,"shelf":756,"authors":1167},"\u002Fblog\u002Fhow-to-write-meeting-minutes","如何撰写会议纪要：格式、模板、示例——以及如今由谁来撰写（2026）","会议纪要是会议的正式书面记录：做出了哪些决定、谁投了票、谁在何时之前负责什么。本文介绍纪要的格式、可直接复制的模板、一份填写完整的示例、董事会会议的补充要点，以及这种格式从未问过的问题：这份记录以谁的语言送达？","\u002Fblog\u002Fhow-to-write-meeting-minutes.svg",[1168],{"name":9},{"path":1170,"title":1171,"description":1172,"image":1173,"date":1152,"topic":777,"genre":755,"shelf":756,"authors":1174},"\u002Fblog\u002Fsales-follow-up-email","销售跟进邮件:通话后的模板,以及如何让通话纪要自动发送(2026)","销售跟进邮件会重述通话中谈到的内容、已做出的决定,以及带有日期的下一步行动,并且在当天发出。本文提供五个适用于常见场景的模板、发送时机规则、如何通过密送(BCC)将邮件同步到 HubSpot、Pipedrive 和 Zoho 的 CRM(含其文档中说明的条件),以及一种无需任何人手动复制、即可自动生成通话纪要并归档到潜在客户记录中的设置方案。","\u002Fblog\u002Fsales-follow-up-email.svg",[1175],{"name":9},{"path":1177,"title":1178,"description":1179,"image":1180,"date":1181,"topic":873,"genre":755,"shelf":756,"authors":1182},"\u002Fblog\u002Fsesli-cevirmen","土耳其语语音翻译器：动词在句末出现，这决定了您需要哪一种","土耳其语把动词、否定和时态都放在句子的末尾。仅凭这一点，就能区分以“语音翻译器”名义出售的三类产品：手机应用、翻译耳机，以及会议实时翻译。本文说明它们各自能处理和无法处理土耳其语句子的哪些方面，以及为什么供应商宣称的语言数量对这一语言对毫无参考价值。","\u002Fblog\u002Fsesli-cevirmen.svg","2026-09-01",[1183],{"name":9},{"path":1185,"title":1186,"description":1187,"image":1188,"date":1189,"topic":953,"genre":914,"shelf":756,"authors":1190},"\u002Fblog\u002Fmeet-in-the-side-panel","在侧边栏中开会:InterMIND Chrome 扩展程序现已上线","该扩展程序已在 Chrome 应用商店上架。它将 InterMIND 停靠在 Chrome 的侧边栏中,紧邻您正在演示的标签页——通话、聊天和参会者始终可见,而标签页仍可由您自由编辑。本文说明它会安装什么、会请求哪些权限,以及它不会做什么。","\u002Fblog\u002Fmeet-in-the-side-panel.svg","2026-08-31",[1191],{"name":9},{"path":1193,"title":1194,"description":1195,"image":1196,"date":1197,"topic":1198,"genre":755,"shelf":756,"authors":1199},"\u002Fblog\u002Fdsgvo-messenger-unternehmen","面向企业的 GDPR 合规即时通讯工具(2026):各供应商实际公开了哪些文档","“GDPR 合规”并不是一张证书,而是一系列由您作为控制者承担的义务。本指南选取 DPO 无论如何都会问的六项检查——数据处理协议、服务器位置、加密、元数据、删除、子处理者——并将其应用于十二种消息服务:WhatsApp、Signal、Telegram、Threema Work、Teamwire、Wire、Stackfield、Element、Mattermost、Rocket.Chat、Microsoft Teams、Slack,以及 InterMIND。仅列出有文档记录的事实,并附上来源和核查日期。","\u002Fblog\u002Fdsgvo-messenger-unternehmen.svg","2026-08-27","alternatives",[1200],{"name":9},{"path":1202,"title":1203,"description":1204,"image":1205,"date":1197,"topic":994,"genre":755,"shelf":756,"authors":1206},"\u002Fblog\u002Fexport-teams-chat","如何导出 Microsoft Teams 聊天记录(2026):用户能做什么、管理员能做什么,以及历史记录为何会丢失","Teams 客户端中没有“导出”按钮。成员实际可以做的操作包括:复制、通过 Outlook 分享、在添加成员时分享聊天历史、下载会议转录;此外,管理员还有两条有文档记载的导出途径:Teams Export API 和 Purview eDiscovery。同时说明聊天历史消失的官方文档原因:保留策略。以及当聊天历史被设计为长期保存时,聊天导出会是什么样子。","\u002Fblog\u002Fexport-teams-chat.svg",[1207],{"name":9},{"path":1209,"title":1210,"description":1211,"image":1212,"date":1197,"topic":994,"genre":755,"shelf":756,"authors":1213},"\u002Fblog\u002Fexport-whatsapp-chat","如何导出 WhatsApp 聊天记录(2026):“导出聊天”能做什么、不能做什么,以及找不到该选项时怎么办","“导出聊天”会通过手机的分享面板,将单个对话以文本文件的形式发送出去,可选择包含或不包含媒体文件——这就是该功能的全部。本文介绍它的含义、在 Android 和 iPhone 上的位置、为什么对方可以阻止导出、为什么备份与迁移是两回事、为什么在德国找不到该选项,以及当您导出的聊天实际上是团队的会议或工作记录时该怎么办。","\u002Fblog\u002Fexport-whatsapp-chat.svg",[1214],{"name":9},{"path":1216,"title":1217,"description":1218,"image":1219,"date":1197,"topic":1198,"genre":755,"shelf":756,"authors":1220},"\u002Fblog\u002Fgoogle-workspace-alternatives","面向跨语言团队的 Google Workspace 替代方案(2026)","大多数 Workspace 替代方案清单只比较邮箱、存储空间和 Docs 的同类产品。如果您的团队日常沟通涉及多种语言,真正重要的评估维度就不同了:谁能用自己的语言阅读 Chat,谁能用自己的语言听会议,一个月后的历史记录是什么样子,以及这一切存放在何处。本文先以 Google 自身的基线为参照,再从这些维度对比 Microsoft 365、Zoho Workplace、Proton、Nextcloud Hub 和 InterMIND,所有事实均注明来源。","\u002Fblog\u002Fgoogle-workspace-alternatives.svg",[1221],{"name":9},{"path":1223,"title":1224,"description":1225,"image":1226,"date":1197,"topic":777,"genre":755,"shelf":756,"authors":1227},"\u002Fblog\u002Fmeeting-recap","会议纪要:如何撰写,以及通话结束后 Zoom、Teams 和 Google Meet 实际保留什么(2026)","会议纪要是会议中真正会被用到的部分:下次通话时被引用,一个月后被检索,被未参会的人阅读。本文先提供一份简短模板,再逐一给出各平台的文档说明:纪要存放在哪里、谁会收到、谁可以编辑、保留多长时间,以及使用哪种语言。涵盖 Zoom AI Companion、Teams Recap、Google Meet 的 Take notes for me 以及 InterMIND,并附有来源。","\u002Fblog\u002Fmeeting-recap.svg",[1228],{"name":9},{"path":1230,"title":1231,"description":1232,"image":1233,"date":1197,"topic":1198,"genre":755,"shelf":756,"authors":1234},"\u002Fblog\u002Fmicrosoft-teams-alternatives","面向跨语言协作团队的 Microsoft Teams 替代方案(2026)","大多数 Teams 替代方案清单比较的是视频画面、免费版限制和 Office 集成。如果您团队的日常沟通涉及多种语言,真正重要的维度就不同了:谁能用自己的语言阅读沟通空间、谁来为此付费、一个月后历史记录是什么样子,以及所有内容存放在哪里。本文按这些维度对 Slack、Google Workspace、Zoom Workplace、Mattermost、Rocket.Chat、Element、Nextcloud Talk 和 InterMIND 进行比较,并附有来源。","\u002Fblog\u002Fmicrosoft-teams-alternatives.svg",[1235],{"name":9},{"path":1237,"title":1238,"description":1239,"image":1240,"date":1197,"topic":1198,"genre":755,"shelf":756,"authors":1241},"\u002Fblog\u002Fslack-alternatives","适用于跨语言协作团队的 Slack 替代方案(2026)","大多数 Slack 替代方案榜单比较的是集成、免费套餐限制和 huddle 通话质量。如果您团队的频道中使用多种语言,真正重要的维度就不一样了:谁能用自己的语言阅读频道内容,谁能用自己的语言收听通话,一个月后历史记录是什么样子,以及这些数据存放在哪里。本文先介绍 Slack 自身的基线,再围绕这些维度依次分析 Microsoft Teams、Google Chat、Zoom Team Chat、Mattermost、Rocket.Chat、Element、Nextcloud Talk 和 InterMIND,并附上来源。","\u002Fblog\u002Fslack-alternatives.svg",[1242],{"name":9},{"path":1244,"title":1245,"description":1246,"image":1247,"date":1197,"topic":1198,"genre":755,"shelf":756,"authors":1248},"\u002Fblog\u002Fteam-communication-tools","分布式团队的团队沟通工具(2026):空间为每位成员带来什么","团队沟通应用的榜单通常按集成、免费版和视频质量排名。而分布式团队生活在空间本身之中——频道、站会、历史记录——并且往往使用不止一种语言。我们围绕三个问题对十款工具进行了比较,并说明数据托管于何处:消息能否以每位成员的语言呈现、会议是否让所有人都听得懂、一个月后历史记录是什么样子。涵盖 Teams、Slack、Google Chat、Zoom、WhatsApp、Telegram、Mattermost、Rocket.Chat、Element、Nextcloud Talk 和 InterMIND,并附来源。","\u002Fblog\u002Fteam-communication-tools.svg",[1249],{"name":9},{"path":1251,"title":1252,"description":1253,"image":1254,"date":1197,"topic":994,"genre":755,"shelf":756,"authors":1255},"\u002Fblog\u002Fwhatsapp-translate","如何翻译 WhatsApp 消息(2026):内置功能、覆盖范围及其局限","WhatsApp 现已自带消息翻译功能:在设备端运行,长按消息即可翻译,在 Android 上还能自动翻译整个聊天。本文介绍在哪里找到该功能、内置支持哪些语言、尚未支持该功能的手机该怎么办、如何处理语音消息,以及它无法做到的三件事:通话、成员各用不同语言书写的群组,以及可用您自己的语言重读的记录。","\u002Fblog\u002Fwhatsapp-translate.svg",[1256],{"name":9},{"path":1258,"title":1259,"description":1260,"image":1261,"date":1262,"topic":994,"genre":755,"shelf":756,"authors":1263},"\u002Fblog\u002Fmultilingual-customer-support","无需雇用客服人员、无需编写代码的多语言客户支持","一种客户支持方案:每位客户都用自己的语言与您交流,您则用自己的语言回复:在您自己的日历中设置预约页面,在其说明中放置一个可重复使用的会议链接,会议回顾将发送到您的收件箱和 CRM。无需聘请多语言员工,无需翻译软件,也无需进行集成开发。","\u002Fblog\u002Fmultilingual-customer-support.svg","2026-08-17",[1264],{"name":9},{"path":1266,"title":1267,"description":1268,"image":1269,"date":1270,"topic":873,"genre":755,"shelf":756,"authors":1271},"\u002Fblog\u002Fsimultandolmetscher","同声传译员:真人、RSI 平台还是 AI——您的多语言会议需要什么(2026)","“同声传译员”是一种职业;大多数搜索真正想要的,是在发言的同时听到另一种语言的内容。本指南区分了同传箱、RSI 平台和 AI 同声传译,并依据官方文档对比各类工具——Interprefy、KUDO、Wordly、DeepL Voice、Zoom、Teams、Google Meet、InterMIND——同时探讨这些对比所忽略的问题:会议内容究竟有多少能以您的语言呈现,以及数据在何处运行。","\u002Fblog\u002Fsimultandolmetscher.svg","2026-08-13",[1272],{"name":9},{"path":1274,"title":1275,"description":1276,"image":1277,"date":1270,"topic":994,"genre":914,"shelf":756,"authors":1278},"\u002Fblog\u002Ftelegram-ingest-how-it-works","如何将您的 Telegram 聊天导入 InterMIND——并用您自己的语言阅读","InterMIND Telegram 机器人可镜像您的群组、转发您的一对一聊天,并保存您转发的任何内容——单向同步,无需配置任何对话。完整指南:连接您的账户、三条路由规则、哪些内容会进入您的频道,以及哪些内容保持私有。","\u002Fblog\u002Ftelegram-ingest-how-it-works.svg",[1279],{"name":9},{"path":1281,"title":1282,"description":1283,"image":1284,"date":1270,"topic":873,"genre":755,"shelf":756,"authors":1285},"\u002Fblog\u002Ftraduction-simultanee","同声翻译:同传箱、RSI 还是 AI——您的会议该选哪种工具(2026)","“同声翻译”其实涵盖三种情形:同传箱中的口译员、远程同声传译(RSI)以及实时 AI 翻译。本指南将三者区分开来,并对比有据可查的工具——Interprefy、KUDO、Wordly、DeepL Voice、Zoom、Teams、Google Meet、InterMIND——同时提出对比类文章通常忽略的问题:会议内容究竟有多少能以您的语言呈现?","\u002Fblog\u002Ftraduction-simultanee.svg",[1286],{"name":9},{"path":1288,"title":1289,"description":1290,"image":1291,"date":1292,"topic":913,"genre":914,"shelf":756,"authors":1293},"\u002Fblog\u002Fpresent-and-edit-at-the-same-time","演示时,您如何看到会议室里的情况?","共享屏幕后,您就等于在“盲讲”:参会者的面孔、聊天消息、举起的手,都被您正在展示的内容挡在了后面。常见的解决办法只是拆东墙补西墙——悬浮窗会遮住您的内容,第二块显示器在幻灯片进入全屏的那一刻,仍然会丢掉参会者名单。本文梳理各平台的官方说明,以及唯一不需要取舍的那个界面。","\u002Fblog\u002Fpresent-and-edit-at-the-same-time.svg","2026-08-12",[1294],{"name":9},{"path":1296,"title":1297,"description":1298,"image":1299,"date":1300,"topic":873,"genre":914,"shelf":756,"authors":1301},"\u002Fblog\u002Fbundle-of-languages","另一种捆绑方式：围绕沟通本身整合多种语言，而不是围绕英语整合各类应用","办公套件的卖点，是围绕一个只默认使用单一语言的沟通层，捆绑邮件、文档、表格和会议等一系列应用。其实还有另一种捆绑方式：把您团队所使用的每一种语言，都整合到沟通本身之中，与您现有的办公套件并行运行。","\u002Fblog\u002Fbundle-of-languages.svg","2026-08-10",[1302],{"name":9},{"path":1304,"title":1305,"description":1306,"image":1307,"date":1300,"topic":913,"genre":914,"shelf":756,"authors":1308},"\u002Fblog\u002Fgive-every-guest-their-language","让每位嘉宾都使用自己的语言","好的主人不会要求客人去适应——无论是座椅、饮食，还是语言。为什么翻译应当由主办方提供，而不是由“需要”它的参会者自行解决；以及当翻译像光线一样为所有人提供时，会议会发生哪些变化。","\u002Fblog\u002Fgive-every-guest-their-language.svg",[1309],{"name":9},{"path":1311,"title":1312,"description":1313,"image":1314,"date":1300,"topic":970,"genre":914,"shelf":756,"authors":1315},"\u002Fblog\u002Fis-your-meeting-confidential","您的会议是保密的吗?","您在会议中说的话,往往是绝不会写成文字的——可这些会议却经由您从未读过的云服务、模型和数据保留政策运行。三个具体问题,让“保密”不再只是主页上的一个词,而是可以核查的事实,以下是我们对每个问题的回答。","\u002Fblog\u002Fis-your-meeting-confidential.svg",[1316],{"name":9},{"path":1318,"title":1319,"description":1320,"image":1321,"date":1300,"topic":777,"genre":914,"shelf":756,"authors":1322},"\u002Fblog\u002Fthe-meeting-a-week-later","一周后,您的会议内容还有多少以您的语言留存?","实时翻译通常以秒数和语言数量来衡量。但会议真正发挥作用是在会后——被引用的决策、被检索的历史记录、迎头赶上的新成员。这是一份有据可查的审计,涵盖 Zoom、Teams、Google Meet 以及各类 AI 记录工具:通话结束后究竟有哪些内容得以留存,又是以谁的语言留存。","\u002Fblog\u002Fthe-meeting-a-week-later.svg",[1323],{"name":9},{"path":1325,"title":1326,"description":1327,"image":1328,"date":1300,"topic":873,"genre":755,"shelf":756,"authors":1329},"\u002Fblog\u002Ftraductor-de-voz","西班牙语语音翻译器:一句话、一位对话者,还是一整场会议?","英语–西班牙语是需求最高的语音翻译语言对——而“西班牙语语音翻译器”其实指三类不同的产品:手机应用、翻译耳机和实时会议翻译。本文介绍它们各自的工作方式、地区性西班牙语的适配情况,以及哪一种能经得起真实对话的考验。","\u002Fblog\u002Ftraductor-de-voz.svg",[1330],{"name":9},{"path":1332,"title":1333,"description":1334,"image":1335,"date":1300,"topic":1198,"genre":755,"shelf":756,"authors":1336},"\u002Fblog\u002Fzoom-alternatives","面向多语言会议的 Zoom 替代方案(2026)","大多数 Zoom 替代方案清单比较的都是 Zoom 已经具备的视频功能。如果您的会议跨越多种语言,真正重要的维度则有所不同:谁能以自己的语言实时参会、每位听众的成本是多少,以及通话结束后能留下什么。本文围绕这些维度,对 Microsoft Teams、Google Meet、Webex 和 InterMIND 进行对比,并附有来源。","\u002Fblog\u002Fzoom-alternatives.svg",[1337],{"name":9},{"path":1339,"title":1340,"description":1341,"image":1342,"date":1343,"topic":913,"genre":914,"shelf":756,"authors":1344},"\u002Fblog\u002Ffree-for-participants","InterMIND 对会议参与者是免费的吗？","是的——对所有参与者免费，无论是否拥有账户。唯一可能需要付费的是主持人，且仅限付费方案。本文说明谁为什么付费、无账户加入意味着什么，以及各项限制的具体所在。","\u002Fblog\u002Ffree-for-participants.svg","2026-08-09",[1345],{"name":9},{"path":1347,"title":1348,"description":1349,"image":1350,"date":1351,"topic":873,"genre":755,"shelf":756,"authors":1352},"\u002Fblog\u002Finterpretation-vs-translation","口译与笔译有何区别:一文讲清各类口译(2026)","口译是将口头语言实时转换为另一种语言,笔译则是转换书面文本。本指南以通俗易懂的方式介绍两者的区别、各类口译(同声传译、交替传译、耳语传译、陪同联络口译)、交付形式(现场、OPI、VRI、RSI、AI),以及哪种方式最适合您的场景。","\u002Fblog\u002Finterpretation-vs-translation.svg","2026-08-08",[1353],{"name":9},{"path":1355,"title":1356,"description":1357,"image":1358,"date":1359,"topic":962,"genre":914,"shelf":756,"authors":1360},"\u002Fblog\u002Fpartner-program-how-it-works","只有您盈利,我们才盈利:InterMIND 合作伙伴模式如何运作","我们合作伙伴计划的完整机制,从头到尾一一说明:哪些永久免费,哪些部分我们按收入分成,季度申报如何进行,我们如何在不进行审计的情况下完成核实,以及合作伙伴受到哪些保护。本文旨在让您无需任何一次澄清电话即可做出决定。","\u002Fblog\u002Fpartner-program-how-it-works.svg","2026-08-02",[1361],{"name":9},{"path":1363,"title":1364,"description":1365,"image":1366,"date":1367,"topic":873,"genre":755,"shelf":756,"authors":1368},"\u002Fblog\u002Ftraduttore-inglese-italiano-vocale","英语—意大利语语音翻译器:适用于一句话,也适用于一场对话","英语—意大利语语音翻译器可以很好地处理一句话,比如一份菜单、一条路线指引。而英语和意大利语使用者之间的工作通话,则是另一项任务。两者各自能做什么,界限又在哪里。","\u002Fblog\u002Ftraduttore-inglese-italiano-vocale.svg","2026-07-20",[1369],{"name":9},{"path":1371,"title":1372,"description":1373,"image":1374,"date":1367,"topic":873,"genre":755,"shelf":756,"authors":1375},"\u002Fblog\u002Ftraduttore-rumeno-italiano-vocale","罗马尼亚语–意大利语语音翻译器:适用于一句话,也适用于一场对话","罗马尼亚语–意大利语语音翻译器能很好地处理一句话——一个方向、一种表达形式。而罗马尼亚语和意大利语使用者之间的工作或家庭通话,则是另一回事。本文介绍两者各自的作用,以及它们的界限所在。","\u002Fblog\u002Ftraduttore-rumeno-italiano-vocale.svg",[1376],{"name":9},{"path":1378,"title":1379,"description":1380,"image":1381,"date":1382,"topic":873,"genre":755,"shelf":756,"authors":1383},"\u002Fblog\u002Fhindi-to-english-voice-translator","印地语到英语语音翻译器——以及英语到印地语——在真实对话中实时翻译","如果只是翻译一句话,找到一款印地语–英语语音翻译器很容易;但要用于真实对话——客户电话、面试、家人间的闲聊——却出人意料地困难。本文介绍三类工具,以及能够实时翻译印地语 ↔ 英语、同时支持双向的那一款。","\u002Fblog\u002Fhindi-to-english-voice-translator.svg","2026-07-19",[1384],{"name":9},{"path":1386,"title":1387,"description":1388,"image":1389,"date":1390,"topic":873,"genre":755,"shelf":756,"authors":1391},"\u002Fblog\u002Flinguee-tradutor-ingles-portugues","Linguee 英葡词典:它的真正用途(以及何时需要换用其他工具)","Linguee 并不是普通的翻译工具,而是一部以数百万条真实语境译文为基础的词典。本文介绍它无可替代的场景、因设计所限而力有未逮之处,以及在连续文本、文档或语音对话这几类任务中应该改用哪种工具。","\u002Fblog\u002Flinguee-tradutor-ingles-portugues.svg","2026-07-17",[1392],{"name":9},{"path":1394,"title":1395,"description":1396,"image":1397,"date":1390,"topic":873,"genre":755,"shelf":756,"authors":1398},"\u002Fblog\u002Ftradutor-de-voz","在线语音翻译器,实时:这些词究竟承诺了什么","每一款语音翻译器都在宣传同样的三个词——在线、免费、实时。但这三个词对应的是三类不同的产品:手机应用、翻译耳机和实时会议翻译。本文解析每个词的真实含义,以及哪类产品能经得起真实对话的考验。","\u002Fblog\u002Ftradutor-de-voz.svg",[1399],{"name":9},{"path":1401,"title":1402,"description":1403,"image":1404,"date":1390,"topic":994,"genre":755,"shelf":756,"authors":1405},"\u002Fblog\u002Ftranscrever-audio-whatsapp","如何转录 WhatsApp 语音消息——以及音频使用另一种语言时该怎么办","WhatsApp 已可在设备端转录语音消息,并保持端到端加密不受影响。本文介绍在哪里开启该功能、它常见的失败情形、为什么第三方转录应用是一笔不划算的交易,以及当真正的问题是语言而不是音频时该怎么办。","\u002Fblog\u002Ftranscrever-audio-whatsapp.svg",[1406],{"name":9},{"path":1408,"title":1409,"description":1410,"image":1411,"date":1412,"topic":873,"genre":755,"shelf":756,"authors":1413},"\u002Fblog\u002Fairpods-live-uebersetzung","AirPods 实时翻译:它擅长什么,以及会议需要更多功能的场景","AirPods 实时翻译是一款出色的面对面翻译工具——一个人说话,翻译直接传入您的耳中,全部在您的设备上完成。本文介绍它的工作原理、语言与硬件限制,以及为什么多人通话是另一类任务。","\u002Fblog\u002Fairpods-live-uebersetzung.svg","2026-07-13",[1414],{"name":9},{"path":1416,"title":1417,"description":1418,"image":1419,"date":1412,"topic":873,"genre":755,"shelf":756,"authors":1420},"\u002Fblog\u002Fsprachuebersetzer","语言翻译器:语音翻译器究竟如何工作,以及它的局限","“语言翻译器”涵盖文本工具、手机应用、翻译耳机和会议实时翻译,这是四种截然不同的产品。本文介绍它们各自的工作原理、适用场景,以及哪一种能让真正的多语言对话顺畅进行。","\u002Fblog\u002Fsprachuebersetzer.svg",[1421],{"name":9},{"path":1423,"title":1424,"description":1425,"image":1426,"date":1412,"topic":873,"genre":755,"shelf":756,"authors":1427},"\u002Fblog\u002Ftraducteur-vocal","语音翻译器:短语、面对面或实时对话","语音翻译器可将语音转换为另一种语言的语音,但它实际上对应三类不同的产品:手机应用、耳机和实时会议翻译。本文介绍各自的工作原理,以及哪一种能让多人之间的即时对话顺畅进行。","\u002Fblog\u002Ftraducteur-vocal.svg",[1428],{"name":9},{"path":1430,"title":1431,"description":1432,"image":1433,"date":1412,"topic":873,"genre":755,"shelf":756,"authors":1434},"\u002Fblog\u002Ftraduttore-francese-italiano-vocale","法语–意大利语语音翻译器:适用于单句,也适用于对话","法语–意大利语语音翻译器能很好地处理单句,例如菜单或问路。而法语和意大利语使用者之间的对话则是另一项任务。本文介绍两者各自的功能,以及它们的界限所在。","\u002Fblog\u002Ftraduttore-francese-italiano-vocale.svg",[1435],{"name":9},{"path":1437,"title":1438,"description":1439,"image":1440,"date":1412,"topic":873,"genre":755,"shelf":756,"authors":1441},"\u002Fblog\u002Ftraduttore-italiano-russo-vocale","意大利语–俄语语音翻译器:既适用于一句话,也适用于一场对话","意大利语–俄语语音翻译器可以很好地处理一句话,比如一份菜单或一条路线指引。而意大利语和俄语使用者之间的对话,则是另一回事。本文介绍两者各自的作用,以及它们的界限所在。","\u002Fblog\u002Ftraduttore-italiano-russo-vocale.svg",[1442],{"name":9},{"path":1444,"title":1445,"description":1446,"image":1447,"date":1412,"topic":873,"genre":755,"shelf":756,"authors":1448},"\u002Fblog\u002Ftraduttore-spagnolo-italiano-vocale","西班牙语–意大利语语音翻译器：适用于一句话，也适用于一场对话","西班牙语–意大利语语音翻译器能很好地处理一句话，比如一份菜单或一条路线指引。而西班牙语与意大利语使用者之间的对话，则是另一项任务。本文介绍两者各自的作用，以及它们的界限所在。","\u002Fblog\u002Ftraduttore-spagnolo-italiano-vocale.svg",[1449],{"name":9},{"path":1451,"title":1452,"description":1453,"image":1454,"date":1412,"topic":873,"genre":755,"shelf":756,"authors":1455},"\u002Fblog\u002Ftraduttore-vocale","语音翻译器:究竟什么才能翻译实时对话","语音翻译器可将一种语言的语音转换为另一种语言的语音。这一类产品分为三种截然不同的形态:手机应用、翻译耳机和实时会议翻译。本文介绍它们各自的工作原理,以及哪一种更适合真实对话场景。","\u002Fblog\u002Ftraduttore-vocale.svg",[1456],{"name":9},{"path":1458,"title":1459,"description":1460,"image":1461,"date":1462,"topic":1198,"genre":914,"shelf":756,"authors":1463},"\u002Fblog\u002Ffireflies-ai-alternatives","2026 年最佳 Fireflies.ai 替代方案 TOP 9(多语言会议实测)","Fireflies.ai 是一款以英语为先的会议记录工具,但并非唯一选择。我们从价格、支持语言和转录限制三个方面对比了 9 款 Fireflies 替代方案,并探讨了其他榜单忽略的一个问题:当您的会议不只使用一种语言时,会发生什么?","\u002Fblog\u002Ffireflies-ai-alternatives.svg","2026-07-02",[1464],{"name":9},{"path":1466,"title":1467,"description":1468,"image":1469,"date":1462,"topic":1198,"genre":914,"shelf":756,"authors":1470},"\u002Fblog\u002Fotter-ai-alternatives","Otter.ai 替代方案:2026 年 9 款优选(以及何时该切换)","Otter.ai 对使用分钟数设有上限,且仅支持 6 种语言的转录。我们从价格、语言支持和使用限制三个方面对比了 9 款 Otter 替代方案,其中也包括所有会议记录工具都无法解决的一种情况:会议并非只使用一种语言进行。","\u002Fblog\u002Fotter-ai-alternatives.svg",[1471],{"name":9},{"path":1473,"title":1474,"description":1475,"image":1476,"date":1462,"topic":1198,"genre":914,"shelf":756,"authors":1477},"\u002Fblog\u002Fotter-vs-fireflies","Otter 与 Fireflies 对比(2026):哪款 AI 会议记录工具更适合您——以及两者都不适用的情形","客观对比 Otter.ai 与 Fireflies.ai:定价、时长与存储限制、语言支持以及工作流。此外还有两者都难以胜任的场景——使用多种语言进行的会议。","\u002Fblog\u002Fotter-vs-fireflies.svg",[1478],{"name":9},{"path":1480,"title":1481,"description":1482,"image":1483,"date":1462,"topic":873,"genre":755,"shelf":756,"authors":1484},"\u002Fblog\u002Fsimultaneous-interpretation-guide","同声传译:它是什么、如何运作,以及 AI 何时能够胜任","一份通俗易懂的同声传译指南:介绍同声传译箱(同传间)的运作方式、费用构成、同声传译与交替传译的区别、远程同声传译(RSI),以及 AI 传译的适用场景——包括在 Zoom、Teams 和 Meet 中的应用。","\u002Fblog\u002Fsimultaneous-interpretation-guide.svg",[1485],{"name":9},{"path":1487,"title":1488,"description":1489,"image":1490,"date":1462,"topic":873,"genre":914,"shelf":756,"authors":1491},"\u002Fblog\u002Fzoom-interpreter","Zoom 传译：语言传译功能的工作原理、费用，以及何时它并不适用","Zoom 传译详解：语言传译功能的使用要求（套餐、预约会议、自备口译员）、启用方法、9 种默认语言、录制和分组讨论室的表现，它与 Zoom 的 AI 翻译字幕和语音翻译功能有何不同，以及何时 AI 同声传译更为合适。","\u002Fblog\u002Fzoom-interpreter.svg",[1492],{"name":9},{"path":1494,"title":1495,"description":1496,"image":1497,"date":1498,"topic":1198,"genre":914,"shelf":756,"authors":1499},"\u002Fblog\u002Fbest-ai-conference-translation-tools","2026 年会议、活动和会议场景最佳 AI 翻译工具:一份坦诚的对比","面向会议和多语言会议的实时 AI 翻译采购指南。大多数工具只翻译当下的口头发言,然后就止步了。真正区分它们的问题——也是各类榜单从不提出的问题——是它们能翻译会议的多大部分:语音、聊天、笔记、文档、支持,以及会后记录。对比对象包括 Interprefy、KUDO、Wordly、Boostlingo、DeepL、Zoom 和 InterMIND。","\u002Fblog\u002Fbest-ai-conference-translation-tools.svg","2026-06-30",[1500],{"name":9},{"path":1502,"title":1503,"description":1504,"image":1505,"date":1506,"topic":970,"genre":914,"shelf":756,"authors":1507},"\u002Fblog\u002Fgdpr-audit-what-we-closed","我们完成了 GDPR 审计，以下是我们实际落实的整改项","如果没有扎实的工作作为支撑，供应商的“符合 GDPR”标识毫无意义。我们针对数据处理者所承担的 GDPR 义务——数据删除、留存、子处理者、欧盟运行环境——对自身代码库进行了全面审计。以下是我们已完成整改的每一项，并均已对照代码进行验证。","\u002Fblog\u002Fgdpr-audit-what-we-closed.svg","2026-06-21",[1508],{"name":9},{"path":1510,"title":1511,"description":1512,"image":1513,"date":1514,"topic":873,"genre":914,"shelf":756,"authors":1515},"\u002Fblog\u002Fown-voice-translation","用您自己的声音,说您不会的语言","大多数实时翻译工具会用一个单一的机械旁白取代您的声音。InterMIND 则保留您的声音:每位参与者听到的译文,都是以原发言人自己的声音呈现。本文将介绍级联流程如何实现这一点,设置中可选的已保存声音样本会带来哪些补充,以及哪些内容会被存储。","\u002Fblog\u002Fown-voice-translation.svg","2026-06-13",[1516],{"name":9},{"path":575,"title":1518,"description":1519,"image":1520,"date":1521,"topic":873,"genre":914,"shelf":756,"authors":1522},"Microsoft Teams 实时翻译(2026):工作原理、费用及局限","Teams 能实时翻译吗?可以,有三种方式:实时翻译字幕、AI Interpreter 智能体,以及人工传译频道。本文说明各方式所需的许可证(Teams Premium、Microsoft 365 Copilot)、每位用户的费用、支持的语言数量、开启方法,以及决定其是否适合您的会议的各项限制。","\u002Fblog\u002Fteams-live-translation.svg","2026-06-12",[1523],{"name":9},{"path":1525,"title":1526,"description":1527,"image":1528,"date":1521,"topic":873,"genre":914,"shelf":756,"authors":1529},"\u002Fblog\u002Fzoom-live-translation","Zoom 实时翻译：工作原理与局限","Zoom 可以通过三种方式实时翻译会议：翻译字幕、支持五种语言的语音翻译器，以及人工传译频道。本文介绍每种方式的工作原理、费用，以及决定它是否适合您的会议的各项限制。","\u002Fblog\u002Fzoom-live-translation.svg",[1530],{"name":9},{"path":1532,"title":1533,"description":1534,"image":1535,"date":1536,"topic":970,"genre":914,"shelf":756,"authors":1537},"\u002Fblog\u002Fgdpr-compliant-video-conferencing","符合 GDPR 的视频会议(2026):真正需要满足什么(以及一个能够翻译的 Zoom 替代方案)","视频工具首页上的“符合 GDPR”所能说明的,远比您想象的要少。以下是通俗易懂的清单,说明它实际要求什么、Zoom 在哪些方面需要配置,以及一个专为翻译而打造、运行于欧盟的替代方案。","\u002Fblog\u002Fgdpr-compliant-video-conferencing.svg","2026-06-08",[1538],{"name":9},{"path":580,"title":1540,"description":1541,"image":1542,"date":1536,"topic":873,"genre":914,"shelf":756,"authors":1543},"Google Meet 实时翻译(2026):工作原理、费用与局限","Google Meet 能实时翻译吗?可以,有两种方式:翻译字幕(支持 90 多种语言)和 Gemini 语音翻译(六个以英语为基准的语言对)。本文说明各自需要哪种 Workspace 方案、费用多少、如何开启、Meet 是否提供语言传译,以及决定它是否适合您的会议的那个关键限制。","\u002Fblog\u002Fgoogle-meet-live-translation.svg",[1544],{"name":9},{"path":1546,"title":1547,"description":1548,"image":1549,"date":1536,"topic":873,"genre":755,"shelf":756,"authors":1550},"\u002Fblog\u002Freal-time-meeting-translation","实时会议翻译:工作原理与评估方法","实时会议翻译让每位参会者都能以自己的语言实时收听和阅读通话内容。本文介绍它是什么、底层究竟如何运作,以及在您购买之前应当询问的问题。","\u002Fblog\u002Freal-time-meeting-translation.svg",[1551],{"name":9},{"path":1553,"title":1554,"description":1555,"image":1556,"date":1557,"topic":970,"genre":914,"shelf":756,"authors":1558},"\u002Fblog\u002Fwhat-one-intermind-meeting-is-built-from","一场 InterMIND 会议由什么构建而成","这是我们运行时架构图的姊妹篇:不讲您的会议在哪里运行,而是讲它由什么构建而成。本文逐层介绍整个技术栈:哪些层运行我们自己的代码或开源软件,哪些层我们务实地选用专有 SaaS,以及为什么您的大部分数据流经的引擎是我们自研的代码,并配有公开的、采用 BSD 许可的客户端 SDK。","\u002Fblog\u002Fwhat-one-intermind-meeting-is-built-from.svg","2026-06-07",[1559],{"name":9},{"path":1561,"title":1562,"description":1563,"image":1564,"date":1565,"topic":970,"genre":914,"shelf":756,"authors":1566},"\u002Fblog\u002Fwhere-one-intermind-meeting-actually-runs","一场 InterMIND 会议的实际运行位置","按供应商逐一梳理:哪些外部服务会接触您的会议、它们在何处执行,以及各自会处理哪些数据——包括在您的组织所选 AI 网关的欧盟区域内运行的 AI 步骤。","\u002Fblog\u002Fwhere-one-intermind-meeting-actually-runs.svg","2026-05-28",[1567],{"name":9},{"path":1569,"title":1570,"description":1571,"image":1572,"date":1573,"topic":873,"genre":914,"shelf":756,"authors":1574},"\u002Fblog\u002Ffalse-fluency-trap","虚假流利陷阱:当“够用”的英语比没有英语更糟","特内里费空难和阿维安卡空难之后,航空监管机构对此作出了强制性规定。医学文献将其量化到每次患者接诊的差错数量。四十年的国际商务研究在会议室中记录了同样的机制。为什么在共同语言中只具备部分流利度,比根本没有共同语言更糟——附数据。","\u002Fblog\u002Ffalse-fluency-trap.svg","2026-05-25",[1575],{"name":9},{"path":1577,"title":1578,"description":1579,"image":1580,"date":1581,"topic":873,"genre":914,"shelf":756,"authors":1582},"\u002Fblog\u002Fhow-many-languages-do-you-support","“您支持多少种语言?”——为什么我们给出的诚实答案是六个数字,而不是一个","每家供应商都只给出一个语言数量。我们做不到,因为翻译并不是单一产品。以下是 InterMIND 按不同功能界面划分的明细:哪些语言经过筛选、为何筛选,以及我们在网站上公布的内容。","\u002Fblog\u002Fhow-many-languages-do-you-support.svg","2026-05-24",[1583],{"name":9},{"path":1585,"title":1586,"description":1587,"image":1588,"date":1581,"topic":873,"genre":914,"shelf":756,"authors":1589},"\u002Fblog\u002Finside-the-translation-pipelines","深入了解驱动 InterMIND 的四条翻译管线","在 InterMIND 中,并不存在单一的“翻译”。这里有四条管线——语音、聊天、笔记和文档——每条都有各自的引擎、延迟预算和质量范围。本文将介绍从您开口说话,到使用另一种语言的参会者听懂您所说内容之间,究竟发生了什么。","\u002Fblog\u002Finside-the-translation-pipelines.svg",[1590],{"name":9},{"path":1592,"title":1593,"description":1594,"image":1595,"date":1596,"topic":873,"genre":914,"shelf":756,"authors":1597},"\u002Fblog\u002Fwhy-translation-quality-marketing-is-broken","翻译质量营销为何失灵——以及我们公开的内容","每家翻译服务商都会公布支持的语言数量，却没有一家公布基于真实流量的、可验证的语言对质量数据。这一差距为何会影响您下一次的供应商评估——以及我们公开的内容。","\u002Fblog\u002Fwhy-translation-quality-marketing-is-broken.svg","2026-05-13",[1598],{"name":9},{"path":1600,"title":1601,"description":1602,"image":1603,"date":1604,"topic":962,"genre":914,"shelf":756,"authors":1605},"\u002Fblog\u002Fintermind-v1-2-release","不会切换成英语的会议室","历经六周的持续交付,InterMIND 从翻译演示成长为多语言工作空间。按观看者定制的语音、聊天、共享笔记和编辑历史,支持 21 种语言,并配有相应的可审计记录。","\u002Fblog\u002Fintermind-v1-2-release.svg","2026-05-12",[1606],{"name":9},{"path":1608,"title":1609,"description":1610,"image":1611,"date":1612,"topic":777,"genre":914,"shelf":756,"authors":1613},"\u002Fblog\u002Fmultilingual-compliance-meetings","您的 SOP 已经翻译完成,但围绕它们的会议却没有。","受监管行业的团队会对受控文件进行本地化,但跨站点审计、CAPA 评审和检查却仍在使用蹩脚的英语进行。文档管理系统(DMS)解决了文档层面的问题,InterMIND 则解决对话层面的问题。","\u002Fblog\u002Fmultilingual-compliance-meetings.svg","2026-04-25",[1614],{"name":9},{"path":1616,"title":1617,"description":1618,"image":1619,"date":1620,"topic":962,"genre":914,"shelf":756,"authors":1621},"\u002Fblog\u002Fintermind-v1-alpha","InterMIND v1.0.0-alpha — 语言障碍,到此为止","我们正式推出 InterMIND:全球首个视频会议平台,让每位参与者都能使用母语交流,并实现彼此的完美理解。2026 年 6 月前,所有用户均可免费使用。","\u002Fblog\u002Fintermind-v1-alpha.svg","2026-03-01",[1622],{"name":9},[]]