Recipes

Each recipe has a request that works, the sequence of tools the assistant should use and what shows up in Memberfy at the end. Swap the names and values for yours. The assistant may vary the order of the reads; what matters is the result.

All of them assume a connection with the Owner or Admin role, unless stated otherwise.

In Claude, six of these recipes are ready in the + › Connectors › Memberfy menu, already in your language: A course with a sales page, An event with tickets, Invite a class, Issue certificates to the class, Create a template with the brand's art and Create a call for papers, along with the monthly report and reviewing a call's proposals. See Ready-made recipes in the menu.

#1. A course with a sales page

For: an online school or an expert selling a recorded course.

Request:

Build the course "Excel from Scratch" in a new section called Learn: 4 modules (Basics, Formulas, Pivot tables, Charts), with 3 video lessons of about 10 minutes in each. Create the course product for US$ 97, sellable by direct link. Leave everything as a draft and tell me what's missing to start selling.

Tools, in order:

Result: the Learn section, the Courses space Excel from Scratch, the course with 4 modules and 12 lessons, and the Excel from Scratch product as a draft, unlocking the space. The assistant points out that the lesson content (ask for it lesson by lesson, as in recipe 20) and publishing are still missing.

To start selling: "Go ahead and publish the product." (publish_product). With the direct link on, the product shows up in the community's /products catalog, and the buyer pays at checkout.

#2. Group mentoring with recurring meetings

For: a mentor with a cohort that meets every week.

Request:

I want to launch Career Mentoring: a monthly subscription of US$ 90, with a 3-month minimum contract, that unlocks an events space only for mentees. Create the Career Mentoring space in the Programs section, and the 4 meetings in November, on Tuesdays, from 8 to 9:30 p.m., online, with the link https://meet.exemplo.com/mentoria. Leave the plan as a draft.

Tools, in order:

Result: the space, unlocked only for subscribers; the plan with the monthly option as a draft; the four meetings in the space.

Notes: there are no recurring events: the assistant creates one event per date. For the following months, ask again ("create the December meetings, same as November's"). See Contract length.

#3. An event with tickets

For: a community that runs paid in-person meetups.

Request:

Create the November Meetup: in person, 11/15 from 7 to 10 p.m., at Espaço Paulista, Rua Augusta 1500, Consolação, São Paulo, SP. 80 tickets at US$ 20. Use the events space that already exists and publish the ticket.

Tools, in order:

Result: the event in the space, and the ticket on sale with 80 units.

Notes: ticket buyers get access to the space, but aren't yet added to the participant list on their own: ask them to confirm attendance at the event, or follow sales through the ticket.

#4. A plan with monthly, annual and add-ons

For: a SaaS, school or coworking with subscriptions.

Request:

Create the Growth plan: monthly at US$ 25 and annual at US$ 228, both with a 7-day trial, unlocking the Customer Area space. Link the existing Coworking Extension as an add-on. Plan address: growth. Leave it as a draft.

Tools, in order:

Result: the Growth plan with both options as drafts and the add-on linked. Once published, the link is /pricing/growth.

Notes: in annual in installments, paying in installments carries Memberfy's installment interest, paid by the buyer by default. To change who pays, use the dashboard.

#5. The community's weekly summary

For: any community. Works with the Moderator role.

Request:

Put together the week's summary: who joined, the posts with the most comments, the upcoming events with how many confirmed. Then write a summary post for the Feed, in a light tone, and show it to me before publishing.

Tools, in order:

Result: the summary in the conversation and, once you approve it, the post in the Feed.

#6. Replying to comments

For: anyone who does live sessions or posts that draw questions.

Request:

Look at the comments on the post "Tuesday's live: questions" and reply to every question I haven't answered yet, thanking them and saying I'll cover it in the next live. React with 👍 to the ones that just said thanks.

Tools, in order:

Result: the replies under each comment, with your name.

Notes: the replies go out with your name, right away. Ask to see the texts first if you prefer: "show me the replies before publishing".

#7. The revenue chart

For: owner, admin or Finance.

Request:

Make a bar chart of monthly revenue over the last 12 months, and a table of revenue by product for the period. Tell me how many subscribers are past due.

Tools, in order:

Result: the assistant builds the chart and the table in the conversation (in Claude, as an artifact). The amounts are the same as in Monetization › Dashboard, with the platform fee; internal costs don't appear.

With the Reports and charts tools, the same request comes from sales_report with group_by: plan (revenue per month per plan, taken from the statement), and the weekly summary from community_overview and engagement_report.

#8. Spaces with icons and posts with images

For whom: whoever is setting up the community and wants each space recognizable in the menu.

Request:

In the Community section, create three Feed spaces: Introductions, Jobs and Technical questions, each with an icon that matches its theme. Then publish in Introductions a welcome post with this cover image: https://example.com/welcome.png. And put this photo from the last meetup in the Meetups gallery: https://example.com/meetup.jpg.

Tools, in order:

Result: the three spaces in the menu, each with its own icon; the post with its cover; the photo in the gallery. The images are stored in Memberfy: the original link can go offline later.

Notes: if the assistant uses the same icon everywhere, ask "use a different icon for each space, matching its theme". To change it later: "swap the Jobs icon for a briefcase" (update_space). See Images.

#9. Editing what already exists

For whom: whoever published something and wants to fix it.

Request:

In the post "How the community works", swap the cover for an image you generate yourself, with the community's name in green, and pin the post to the top. Then delete the duplicate post with the same title.

Tools, in order:

Result: the post with the new cover, pinned; the duplicate deleted.

Notes: you can also paste the post's link: "Edit this post: https://…". See Content and engagement.

#10. Invite a class

For whom: a school, course or program that takes in a whole class at once.

Request:

Invite these people as members, all in the March class group (create the group if it doesn't exist) and with the tag Student 2026: Ana Souza, [email protected]; Bruno Lima, [email protected]; Carla Dias, [email protected]. Show me the summary before sending.

Tools, in order:

Result: each person gets the invite e-mail (someone without an account gets the link to set a password) and joins the group with the tag. The assistant shows the result for each e-mail: invited, updated (already a member and got the group and the tag) or skipped, with the reason.

Notes: up to 100 people per call; for a bigger class, the assistant splits it. Someone who was already a member doesn't stop the rest. For a whole spreadsheet, with other columns, use the recipe Import a spreadsheet through the assistant. See Members.

#11. Issue certificates to the class

For whom: a school, course or event that certifies people who completed it.

Request:

Issue the completion certificate to the March class group, subject Excel from Scratch, 40 hours. Tell me first how many people will receive it.

Tools, in order:

Result: each person in the class receives the certificate, with the PDF, the image and the verification page, and the email "Your certificate is here". Under Issued, in the Certificates space, the issuing shows up with its progress.

Notes: you can mix people, groups and tags in the same issuing; someone in more than one gets a single certificate. For people who already hold a valid one and should get it again, ask "issue it even to those who already have it". See Certificates.

#12. Create a template with the brand's art

For whom: anyone with ready-made artwork from their designer.

Request:

Create a certificate template with this artwork: https://…/certificate.png. Title Certificate of participation, text "{nome} participou[ de {assunto}]". Show me how it looks.

Tools, in order:

Result: the template, active in the Certificates space, ready to issue.

Notes: the artwork must be at least 2,000 px wide, PNG or JPEG; the certificate comes out in A4 landscape. See Certificates.

#13. Create a call for papers

For whom: an association, a tech community or a company that builds an event's program from outside proposals: a call for papers.

Request:

Open the call for papers for Congress 2027: in person in São Paulo, March 12 and 13, from 9 a.m. to 6 p.m. Tracks Product, Data and Career, each with a short purpose. Proposals until November 30, talks of 20 or 40 minutes and 90-minute workshops. We cover lodging and meals; the speaker covers travel; no speaking fee. Committee review, blind. Make Ana and Bruno reviewers for Data. Leave it as a draft and show me before publishing.

Tools, in order:

Result: the call published in the Call for papers space, with the three tracks, the two days and the Data committee. Proposals start coming in; you follow them with get_review_progress and decide with decide_proposal.

Notes: the call starts as a draft and doesn't show up for members until it's published. Whoever opens the call becomes its owner. Opening a call depends on who can open a call in the space, so a member can use this recipe too, if the space allows it. In Claude, the Open a call for papers recipe in the menu builds the same request from the event, the deadline and the tracks. See Call for papers and Call for papers (the space).

#14. Who did what

For whom: an owner or admin who wants to understand what happened.

Requests:

Notes: the arguments of assistant calls come summarized, with no codes or images. See list_activity_logs.

#15. Everyday questions

For whom: whoever runs the community, and any member for the questions about themselves.

Requests:

Notes: get_community_fees is for admin or finance; get_email_stats, for admin. See Tools.

#16. How much do I have to withdraw, and when is the rest released?

For whom: owner, admin or finance.

Request:

How much do I have to withdraw, and when is the rest released?

Tools, in order:

Result: "You have US$ 400.00 available: you can withdraw up to US$ 398.75. Another US$ 1,200.00 is pending: US$ 300.00 is released on November 9, US$ 500.00 on November 15 and US$ 400.00 on December 1. US$ 48.00 is held as the chargeback reserve and comes back on December 9." Pending and retained money is never offered for payout.

Notes: every sale is released 30 days after payment; on a card sale in installments, each installment on its own date. With a balance in more than one currency, there's one line per currency. See Balance and statement.

#17. Withdraw everything you can

For whom: owner or admin. Finance can ask the questions, but can't request the payout.

Request:

Withdraw everything you can.

Tools, in order:

Result: with US$ 1,000.00 available, the assistant says the maximum is US$ 997.26 (the balance also covers the fee), shows the summary and, after your yes, requests the payout.

Notes: only the available balance is paid out; pending and retained money waits for its release dates. If the maximum doesn't reach the US$ 10.00 minimum (R$ 10.00 in reais), the assistant doesn't offer the payout and says when the next release happens. An amount above the maximum, or below the minimum, is refused on the first call. If the bank refuses it, the payout ends up Failed, with the reason, and the amount and the fee go back to the balance. See Payouts.

In reais, the payout goes to the bank right away, with the credit expected the next business day.

#18. Refund a buyer

For whom: owner, admin or finance.

Request:

Refund [email protected]'s course purchase. She keeps her access: it was an agreed discount.

In Claude, the same request is ready in the menu: Refund a buyer (refund_buyer), with the buyer, access and the reason.

Tools, in order:

Result: "Refund made. US$ 297.00 goes back to Maria by PIX, and she keeps access to the course." If the receiving account doesn't have the balance for the community's part yet, the refund stays pending: waiting for balance, goes out on its own in order of arrival, and the assistant shows with get_balance how much was reserved.

Notes:

• If you don't say, the assistant asks whether access continues. On a subscription, revoking cancels it right away.
• Boleto: Memberfy doesn't give a paid boleto back. The assistant explains that you need to return the money directly to the buyer, by PIX or bank transfer, and asks whether you already did; with your yes, it records the return (it can be partial).
• On card and PIX, it can be just part of it ("return US$ 30 to Maria"); a partial refund usually stays processing for a few minutes. In an order with a plan and add-ons, each purchase is refunded on its own. A purchase with no charge at the provider is refused before the summary, with the reason.
• See Refunds and disputes.

#19. Change your picture and set a featured image

For whom: any role, for their own picture; moderator or above, for the event image and someone else's picture.

Request:

Change my picture to this one: https://example.memberfy.net/me.png. And set this square image as the featured image of the November Meetup: https://example.memberfy.net/meetup-square.png.

Tools, in order:

Result: your new profile picture; the square image as the event's featured image.

Notes: the assistant also accepts an image it generated in the conversation (a file, up to 5 MB). To remove a picture: "remove Maria's picture" (update_avatar with member and remove: true; someone else's needs a role above theirs). See Images.

#20. Build a course with modules and lessons of every type

For whom: a school or expert who wants the course ready, with its content, without opening the dashboard.

Request:

Build the course "Excel from Scratch" in the Courses space that already exists, with two modules. In Basics: a text lesson "Welcome" (write a short introduction yourself), and a video lesson "First steps" with https://www.youtube.com/watch?v=abc123XYZ00, 12:30 long. In Tools: a link lesson "Practice sheet" with https://example.memberfy.net/exercises and an image lesson "Shortcuts" with https://example.memberfy.net/shortcuts.png. Leave it as a draft.

Tools, in order:

Result: the course as a draft, with 2 modules and 4 lessons, each with its content. For a lesson that was missed, or to fix one, the assistant uses create_lesson and update_lesson.

Notes:

• A video is embedded only if it is from YouTube, Vimeo or Loom. If you send another address, the assistant tells you and creates the lesson as a link.
• Text goes in Markdown (headings, lists, bold) and shows up formatted for the student. Links and images must start with http:// or https://.
• The duration is mm:ss or hh:mm:ss. Writing "12 min" is refused, and the assistant fixes it.
• To publish: "Publish the course." (update_course with status: published). See Tools · Courses.

#21. Study a course

For whom: any member, through the assistant.

Request:

Enroll me in the Excel from Scratch course, show me the content of the first lesson and, when I say I have read it, mark it as completed.

Tools, in order:

Result: you are enrolled, the first lesson is read in the conversation and marked as completed. When you finish the last lesson, the assistant says the course is over and suggests looking at your certificates.

Notes: without enrollment, get_course returns only the outline (title, type and duration). complete_lesson with completed: false only records the access; it never un-completes a lesson.

#22. A single-course space, with its course

For whom: a mentor or school with a single program, where the person opens the space and lands straight on the course.

Request:

In the Learn section, create a Courses space called "90-day Mentoring", in A single course mode, with the course "90-day Mentoring", intermediate level. Leave it as a draft.

Tools, in order:

Result: the space and the course as a draft, visible only to the team. The assistant suggests the next step: adding the first module.

Notes: a space in A single course mode has no room for a second course (drafts and archived courses count). To have several again, "switch the space to a list of courses" (update_space with mode: multi), which always goes through. The opposite switch, with 2 or more courses, is refused, and the assistant says how many there are. See Courses.

#23. Build and publish the course

For whom: someone who already has the course as a draft and wants the content in place and live.

Request:

In the "90-day Mentoring" course, create the modules Month 1, Month 2 and Month 3, with two text lessons in each. Put Month 3 before Month 2. Show me how it looks and, if everything has content, publish it.

Tools, in order:

Result: the course published, with 3 modules and 6 lessons, in the requested order.

Notes: the reorder_course_modules list must have all the course's modules; if one is missing or repeated, nothing changes. For a module's lessons, reorder_lessons. Publishing with a lesson with no content makes students see "content coming soon" in it, so it is worth asking the assistant to check first.

#24. Follow the students of a course

For whom: an owner, admin or moderator who wants to know who is moving forward.

Request:

Who is taking the Excel from Scratch course? Show me each one's progress and who has already finished.

Tools, in order:

Result: the list of students with "N of M lessons", the percentage and the date of the last activity, and who finished. If the list comes back empty, the assistant suggests checking whether the course is published and has lessons.

Notes: a canceled enrollment does not count. For the moderator the list is read-only; members don't have this tool.

#25. Set up this course's certificate

For whom: an owner or admin who wants the certificate to go out by itself when the student completes.

Request:

Turn on the certificate for the course "Excel from Scratch". Show me the active templates and use Course completion. Before turning it on, tell me who will receive it.

Tools, in order:

Result: the course starts issuing. The assistant warns that whoever completes from now on gets the certificate by email, and whoever already completed does not.

Notes: without template_id, the platform default applies. To change the text, send text (plain text, up to 5,000 characters, with {nome}, {assunto} and {cargaHoraria}). To turn it off, enabled: false. If the template is archived later, the course stops issuing and the assistant warns you. See Certificate on completion.

#26. What does the course issue?

For whom: an owner or admin checking the setup.

Request:

Which of my courses issue a certificate, and with what template? Is any of them stuck?

Tools, in order:

Result: the list of courses that issue and those that do not and, for those whose template is archived or deleted, the warning that nothing is being issued, with the suggestion to pick another template.

#27. I finished the course

For whom: any member, through the assistant.

Request:

Mark the last lesson of the course Excel from Scratch as completed and tell me if the certificate came out.

Tools, in order:

Result: the course completed and the certificate in My certificates. A course that does not issue creates no certificate and no suggestion.

#28. Turn on my event's certificate

For whom: an owner or admin who wants the certificate to go out on its own after the event.

Request:

Turn on the certificate for the event "November Meetup". Use the Platform default and tell me who will receive it.

Tools, in order:

Result: the event starts issuing. The assistant warns that whoever has "going" when the event ends gets the certificate by email about 1 hour later, that there is no check-in yet (someone who confirmed and did not go also gets it) and that an event that already ended does not issue.

Notes: the event needs an end time. Without template_id, the Platform default applies. To change the text, send text. To turn it off, enabled: false. See Attendance certificate.

#29. Post an ad in the classifieds

For whom: any member who can post in the space.

Request:

In the Neighborhood classifieds space, post an ad in the For sale category: "29-inch bicycle", $800, for 15 days, with this photo.

Tools, in order:

Result: the ad is live until the term's date. If the space requires approval, the assistant says it appears after the team approves.

Notes: the term must be one of the allowed ones and does not change later. Value only if the space shows value: it is information, the platform charges nothing.

#30. Who is interested in my ad?

For whom: the ad's author, or the team.

Request:

Who is interested in my bicycle? Mark as answered the ones I already got back to.

Tools, in order:

Result: the list of interested people and the status of each. The conversation continues outside the platform, through the account contact.

#31. Send a campaign to a group

For whom: owner or admin.

Request:

Create a campaign called "Opening class" for the March cohort group, with a welcome text and a button to the community. Show who receives it, send me a test and, if it looks right, send it.

Tools, in order:

Result: the campaign accepted, with the e-mails going out in batches. The assistant warns that the send cannot be undone.

Notes: moderators and finance do the first three steps, but do not send. Someone who unsubscribed never enters the audience.

#32. How many sends do I have left?

For whom: the team.

Request:

How many campaign sends can I still make today and this week? And who unsubscribed?

Tools, in order:

Result: the quota in sends (never cost) and the list of who asked not to receive.

#33. Join a lesson's discussion

For whom: an enrolled student, or the team.

Request:

Comment on the "Welcome" lesson of the Excel from Scratch course that I liked the spreadsheet example, and reply to Ana's comment thanking her.

Tools, in order:

Result: the comment appears at once for the cohort. You can only reply to a comment, not to a reply.

#34. Set up a course's instructor and leaderboard

For whom: owner or admin.

Request:

On the Excel from Scratch course, set Carla as the instructor, list three things people will learn and turn on the course leaderboard.

Tools, in order:

Result: the course page starts showing the instructor, the list of what people learn and the top 10 leaderboard.

#35. Schedule a campaign

For whom: owner or admin.

Request:

Schedule the "Opening class" campaign for every Monday at 9 am. Check the quota first and show me the summary.

Tools, in order:

Result: the campaign scheduled, in the community's time zone. Each send uses one send of the quota when it goes out.

#36. Turn on "Weekly updates"

For whom: owner or admin.

Request:

Turn on the community's weekly summary, every Friday at 10 am, with only new posts and events.

Tools, in order:

Result: the automatic on. A week with nothing new, it does not send.

#37. Create a quiz in a lesson

For whom: owner or admin.

Request:

In the SQL lesson, create a quiz with 3 multiple-choice questions, passing score 70, and explain each answer.

Tools, in order:

Result: the quiz lesson created. The student only sees the answer key after passing.

#38. Host a video in a lesson

For whom: owner or admin.

Request:

Create the lesson "Welcome" in module 1 as a video, with no link, and host this MP4: https://…/welcome.mp4

Tools, in order:

Result: the lesson with the hosted video. Only enrolled people with the lesson unlocked, and the team, see it; the playback link is temporary.

#39. Set up the coworking's Attendance and the front desk kiosk

For whom: owner or admin (the moderator only generates the link).

Request:

Create the Attendance space for the Downtown location in the Coworking section: members can mark their own arrival, capacity of 60, automatic check-out at 10 p.m., and ask for the guest's company name. Then generate the kiosk link for the front desk iPad.

Tools, in order:

Result: the Attendance · Downtown space with the settings you asked for and the kiosk link. The assistant warns that the link is secret, that it should be opened on the iPad (with Add to Home Screen) and that, if lost, it has to be revoked and a new one generated.

Notes: the kiosk's privacy notice is up to the community; it's a good idea to post a notice at the front desk. See Data and privacy.

#40. Who's here and the guest who just arrived

For whom: the team (owner, admin, moderator or finance).

Request:

Who's at the Downtown location right now? And register the guest Pedro Alves, from Acme, who's here to see Ana.

Tools, in order:

Result: Pedro on the list and in the occupancy, and Ana notified by email (up to 10 per hour for each host). Registering the same name with the same host again doesn't duplicate it.

#41. I've arrived, I'm leaving and my month

For whom: any member, in a space that lets members mark with the button.

Request:

Record my arrival at the Downtown location. At the end of the day, my departure. And tell me how many days I went this month.

Tools, in order:

Result: the visit closed and the month's summary. If the space is Only the team, the assistant explains that arrival is marked by the front desk. Forgot to check out: the team fixes it with update_visit (today), or the system closes it at 23:59.

#42. Receive a parcel with a photo and notify the member

For whom: the team (owner, admin, moderator or finance).

Request:

An Amazon package arrived for Maria Souza, tracking BR123456789, in locker 12 with code 4821. Here's the photo: [link].

Tools, in order:

Result: the parcel in Waiting for pickup and Maria notified by email, with the photo thumbnail, the place and the code. The assistant mentions that the email goes out and doesn't repeat the code. Registering the same package again within 24 hours is refused, unless you confirm it's a different one.

#43. Do I have a parcel? And my pickup

For whom: any member.

Request:

Do I have any parcel waiting? I already picked up the one in locker 12.

Tools, in order:

Result: the assistant shows what's waiting for you and, after the pickup, marks it as picked up. If the community requires team confirmation, it explains that the pickup is confirmed at the front desk.

#44. Clear the stalled queue: return, discard and reopen

For whom: the team (discard and reopen: owner or admin).

Request:

Which parcels have been stalled for more than 3 days? Return John's to the sender and discard the ones nobody claimed.

Tools, in order:

Result: the parcels closed, each with its reason, and nothing deleted: everything stays in the history. If it was a mistake, reopen_parcel reopens it (and update_parcel sets another code). Photos or records made by mistake are removed with remove_parcel_photo and delete_parcel, which ask for your yes first.

#45. Set up the coworking's Bookings, with prices and credits

For whom: owner or admin.

Request:

Create a Bookings space called "Rooms", open Monday to Friday, 8 AM to 7 PM. Add Room 1 (8 people, projector and TV) at 3 credits per 30 minutes and Room 2 (4 people) for free. On the Resident plan, give 40 credits a month.

Tools, in order:

Result: the space with both rooms, Room 1 charging credits and Room 2 free, and the plan granting 40 credits a month. If the community had no Bookings space, the assistant would create the space before setting the credits.

#46. Book a room knowing the cost and the balance

For whom: any member.

Request:

I need a room for 6 people tomorrow from 2 to 4 PM, with a projector. How much does it cost and how many credits do I have? Book the cheapest one.

Tools, in order:

Result: the booking confirmed, the credits debited and the email with the calendar invite. If the time was taken, the assistant offers the next free ones; if credits are short, it says how many.

#47. Reschedule and cancel without losing credits

For whom: any member.

Request:

Move my booking from Thursday to Friday, same time. And cancel Monday's.

Tools, in order:

Result: the booking moved (the credit difference debited or refunded) and the other one canceled. Within the cancellation window (24 hours by default), the credits come back; after it, they may be lost.

#48. Block a room for maintenance and cancel the bookings

For whom: the team (owner, admin, moderator or finance).

Request:

Block Room 1 on Tuesday from 9 AM to noon for air conditioning maintenance and let whoever had a booking know.

Tools, in order:

Result: the period blocked, the bookings canceled with the credits refunded in full and each person told by email with the reason, with the event canceled in their calendar.

#49. Grant credits, adjust and change the rules

For whom: owner, admin or finance (the rules: owner or admin).

Request:

Give Maria 10 courtesy credits, valid until the end of the month, for referring a member. Show her statement. Then turn on credit accrual with a cap of 20.

Tools, in order:

Result: a new batch of 10 credits with the reason in the statement, and accrual on from the next month turnover, without changing existing batches. To take credits away, the assistant uses revoke_credits and asks for your yes.

#50. Approve members' mentoring agendas

For whom: owner or admin.

Request:

Is any mentor agenda waiting for approval? Approve Ana's and show me who has free time this week.

Tools, in order:

Result: Ana's agenda starts showing in members' search. The hours a member offers are always free.

#51. How is the community today?

For whom: owner, admin, moderator or finance. The moderator doesn't get the money part.

Request:

How is the community today? Tell me first what needs my attention and then the week's numbers against the previous one.

Tools, in order:

Result: a short summary, with what is urgent on top. Money only comes for owner, admin and finance. See Reports and charts.

#52. Register a guest

For whom: any member with access to the Visitors space (the team also registers on behalf of a host).

Request:

Register Maria Souza ([email protected]), from Acme, as my guest tomorrow from 2 pm to 3 pm, and notify Maria by email.

Tools, in order:

Result: the guest as Expected. The assistant tells you what goes out by email: the confirmation to you (if the space confirms to the host) and the notice to Maria only if the space allows it; if the email to the guest is turned off, it tells you. It also reminds you that the registration keeps a third party's data. For another day, update_visitor_invitation; to give up, cancel_visitor_invitation, which asks for your yes first.

Notes: the team registers on behalf of someone else with search_visitor_hosts and host_member_id.

#53. Front desk: who I'm expecting and who arrived

For whom: the team (owner, admin, moderator or finance).

Request:

Who am I expecting today at the Downtown location? Maria Souza just arrived, mark the arrival. Oh, that was a mistake: undo it.

Tools, in order:

Result: Maria as Arrived, in the occupancy and in Attendance's Who's here. The assistant says whether the host was notified. Undoing puts the registration back to Expected. Whoever didn't show up becomes Did not show up on its own the next day, with no action.

Notes: a guest who arrives without a registration is still check_guest_in, from Attendance.

#54. Open a ticket with a photo

For whom: any member with access to the Support space.

Request:

The projector in Room 3 hasn't turned on since yesterday. Open a maintenance ticket, Equipment category, with this photo.

Tools, in order:

Result: the ticket as Open, with the photo stored privately and its number (#42). The assistant tells you whether the room already had open tickets, shows the category's expected time (an estimate, not a guarantee) and lets you know the team was notified. To send another photo later, add_support_photo.

Notes: if the team opens the ticket for a resident, the assistant first shows who will receive the email.

#55. Triaging the ticket queue

For whom: the team that answers (owner, admin and, depending on the settings, moderator and finance).

Request:

Triage Support: show me what's overdue and what's unassigned. Assign the Internet ones to Pedro and raise the priority of whatever has gone longest without an answer.

Tools, in order:

Result: the queue organized, with each change recorded in the ticket's conversation and Pedro notified by email of each assignment. If a ticket is in a category you don't answer, the assistant says the API refused it and goes on with the rest.

Notes: the assignee must answer the ticket's category. To resolve, update_support_ticket with status: RESOLVED and message.

#56. Add an internal note to a ticket

For whom: the team that answers the category.

Request:

On ticket #42, add an internal note that the technician is coming on Thursday and the quote is 300 reais. Don't notify the resident.

Tools, in order:

Result: an internal note in the conversation, which only the team reads. The resident doesn't see it and gets no email. The assistant confirms this. To answer the resident, the same request without "internal note" (internal omitted).

#57. A campaign that calls each person by name and by leader

For whom: the team writes and tests; the owner or an admin sends.

Request:

Create a campaign for the Product group with the subject "{{first_name}}, your climate survey is here" and a text saying that the leader {{leader|of your area}} will talk to each person. Which variables exist? Send me a test.

Tools, in order:

Result: the draft ready; each person in the group will read their own name and their own leader, and someone with no leader reads "of your area". A misspelled variable is refused before saving, with the field and the name.

Notes: with no fallback, an empty variable vanishes without leaving a double space. Avoid {{tags}} if the community uses internal tags. See Per-recipient variables.

#58. Find a product and feature it in the store

For whom: owner or admin.

Request:

Find the product "Diamond Tier" and feature it in the store.

Tools, in order:

Result: the product gets the Featured badge and, in a store that shows every product, appears first. See Store.

Notes: to feature several at once, update_products. In a store with chosen products, the order stays the one you set.

#59. Take the room out of use from the ticket and see the report

For whom: the team that answers the category.

Request:

The air conditioning in the Blue Room broke (ticket #57). Take the room out of use from today at 2 p.m. until tomorrow at 6 p.m., canceling the bookings with a refund. Then show me this month's Support report.

Tools, in order:

Result: the room blocked for the period, whoever had a booking notified by e-mail and with their credits back, and the month's report. Once the repair is done, reopen_resource_for_ticket returns the room.

#60. A tablet at the room's door

For whom: owner, admin or moderator.

Request:

Create the door panel link for the Blue Room for the new tablet and turn on releasing the room when nobody starts the meeting within 10 minutes.

Tools, in order:

Result: the link to open on the tablet and the rule turned on: a booking nobody starts within 10 minutes releases the room. See Door panel.

Notes: a lost tablet is switched off with revoke_room_panel. Whoever booked can also start from the conversation, with check_in_booking.

#61. Import a spreadsheet through the assistant

For whom: an owner or admin with a list in .xlsx or .csv (an event's attendees, a member base).

Request: attach the spreadsheet to the conversation and write:

Import the members in this spreadsheet into the Members 2026 group. The origin is "Active members of 2026". Show me the summary before importing.

In Claude, you can also pick the ready-made recipe Import members from a spreadsheet from the Memberfy menu.

Tools, in order:

Result: the new people join the group and get the invitation with the origin and the decline link; existing members get the group, with no e-mail. The report lists the skipped rows and the reason; get_member_import_file brings their CSV.

Notes: the origin is required and goes in the e-mail; without a consent column, the assistant asks for your declaration that everyone agreed. Spreadsheets up to 5 MB, 5,000 rows and 100 columns. The import only gives the member or moderator role. See Import members from a spreadsheet and Members.

#62. Send to 2023 + 2025, minus those in 2026

For whom: owner or admin.

Request:

Create a campaign "Come back for the 2026 edition" for the groups Inscritos 2023 and Inscritos 2025, excluding anyone already in Inscritos 2026. Tell me how many receive it before sending.

Tools, in order:

Result: whoever signed up in 2023 or 2025 and is not yet in 2026 receives it once; someone in both 2025 and 2026 is left out.

Notes: the exclusion also takes tags and member_ids, and applies over all: true. See The audience.

#63. Who was active, who joined and what was sent

For whom: the team (owner, admin, moderator and finance).

Requests:

Who was active in the last 7 days?

Who joined this month?

Which campaigns were sent last week?

Tools, in order:

Result: the same lists the Dashboard opens. In the first one, the total is the Active members card's number.

Notes: the dates are days in the community time zone, both ends included. Whoever joined and already left does not show up in the second list, so it can have fewer people than Growth's "joins". See list_members and E-mail campaigns.

#64. What did Maria do this week?

For whom: the team (owner, admin, moderator and finance).

Request:

What did Maria Souza do this week? And did the community's engagement grow compared with last week?

Tools, in order:

Result: the list of what Maria did, day by day, and a sentence like "Compared with last week: active members +8%, comments +15%, reactions −3%." With two Maria Souzas, the assistant asks which one (by e-mail).

Notes: the same list is on the Engagement page, which exports it as CSV. See list_engagement_activities.

#65. Who made Ana an admin?

For whom: owner or admin.

Request:

Who made Ana an admin, and when? Did she change any settings after that?

Tools, in order:

Result: who gave the role, when and whether it was through the app or an assistant, and the changes Ana has made since then.

Notes: the Logs never bring secrets, bank details or fees. See list_logs and Logs.

#66. Where visits come from and where checkout loses people

For whom: owner or admin (finance sees only the funnel).

Request:

How many visits did we get in the last 30 days, where did they come from, and at which checkout step do people give up the most?

Tools, in order:

Result: a summary with the visits and their source, and the step where the funnel loses the most. The assistant talks about "visits", not "unique people": the same person on different days counts more than once.

Notes: for who is in the app right now, get_online_now. See analytics_report.

#67. Find the duplicate photos in the gallery

For whom: whoever looks after the gallery (whoever added the photos, or moderator, finance and up to delete other people's).

Request:

In the Meetup 2026 gallery, are there duplicate photos? Show me the copies and delete them, keeping one of each.

Tools, in order:

Result: the list of duplicate photos, which one stays and which go, and the copies deleted after confirmation.

Notes: the links last about 1 hour (url_valid_seconds says how much is left); in a large gallery, the assistant lists again or uses get_media_url when they expire. A photo still processing has no link: list again in a few seconds. See list_gallery_images.

#68. Ask the community with a poll

For whom: owner, admin or moderator.

Request:

Create a poll in the Feed asking which month is best for APICON Rio, with March, April and May. It closes on the 30th at 11:59 pm. Then tell me how it's going.

Tools, in order:

Result: the poll in the Feed, with the Poll badge and Closes on 30/…; members vote in the app or through the assistant itself (vote_poll).

Notes: in a Content space, the question becomes the post title. The percentage is of the people who voted. In Claude, the recipe Ask the community (poll) already builds this request. See Polls.

#69. Register a company

For whom: owner or admin.

Request:

Register Acme Tecnologia as a company: private office, since 11/1, able to buy the Private office monthly plan. Invite the partner, [email protected], make her the company admin so she can add the rest of the team, and give me the purchase link to send her.

Tools, in order:

Result: the company in Administration › Members, Companies section, with Maria on the team and the Company admin badge, and the purchase link in the conversation. Maria opens the link, buys the plan in My company › Purchase with Acme's CNPJ (in the app: the assistant takes no card) and invites her colleagues, who get the plan's access.

Notes: the assistant warns first that the invite sends an e-mail. A person is on one company only. See Tools · Companies and Companies.

#70. Invite a colleague to your company

For whom: the admin of a company (usually a member) and the invited colleague.

Request from the company admin:

Invite [email protected] to my company's team.

Request from the colleague, after the e-mail:

Do I have any company invitation? If it is from Acme, accept it.

Tools, in order:

Result: João on Acme's team, in My company; the invitation leaves Pending invitations.

Notes: the company admin's invite never links right away, not even someone already in the community. Declining (decline_company_invitation) asks to confirm and is final. Once the company is closed, its admin no longer invites. See Tools · Companies.

#71. Walk the 2nd floor round

For whom: owner, admin or moderator (setting up the sector is for the owner or the admin).

Request:

Start the 2nd floor round. Room 3 and Room 4 are OK, the kitchen bulb near the window is burnt out (photo attached) and I couldn't check the restroom. Then complete the round.

Tools, in order:

Result: the completed round in Round history, with 2 OK, 1 problem and 1 pending, and the kitchen ticket in the Support queue with the Opened in the 2nd floor round badge.

Notes: only deleting a sector or a spot asks for confirmation. A spot that opened a ticket can't go back to OK. In Claude, the Inspection round recipe (run_inspection_round) already builds this request. See Tools · Support and Inspection rounds.

#72. What I get through my company

For whom: anyone on a company's team (usually a member).

Request:

What do I get through my company? How many of its credits can I use?

Tools, in order:

Result: the answer lists, for example, Private office monthly (plan), which unlocks the Meeting rooms and Wall spaces, and 18 company credits, 5 of them expiring at the end of the month. Nothing changes in Memberfy. It is the same as the What you get through your company card on My company › Team.

Notes: no prices or billing: those are only for the company admin. With the company closed, benefits is empty and the assistant says the company no longer gives access. To book with these credits, see Bookings (pay_with: company). See Tools · Companies.

#73. Which API keys do I have?

For whom: any role.

Request:

Which API keys do I have in this community, and what can each one do?

Tools, in order:

Result: the list of your keys, for example Calendar (active, Bookings · read, used 2 hours ago) and Old spreadsheet (expired). Nothing changes in Memberfy.

Notes: the secret never shows up. To create, rename, change IPs or revoke, use the Integrations & APIs screen: the assistant only lists. See list_integrations.

#74. Which community keys are active?

For whom: owner or admin.

Request:

Which of the community's API keys are active, whose are they and what can they do? Did any refuse a call because of the IP?

Tools, in order:

Result: each active key with its owner and what it reaches, and the ones that had a call refused by IP (with the IP and when). Nothing changes in Memberfy.

Notes: to see one person's keys only, ask by name: the assistant finds the member and passes member_id. Revoking is on screen, in All in the community. With another role, the assistant answers that only owner and admin see everyone's keys.

#75. What did the n8n key do?

For whom: owner or admin.

Request:

What did the n8n key do this week? Was any call refused?

Tools, in order:

Result: what the key created or changed during the week, with the result of each call, and the refusals (blocked action, IP outside the list, per-minute limit).

Notes: reads are not recorded: only writes, deletions and changes to the keys. A repeated refusal shows up at most once per minute. See Logs › API keys.

#76. Is any app or webhook failing?

For whom: owner or admin.

Request:

Is any integration or webhook failing? Why?

Tools, in order:

Result: which ones are Failing or Disabled after failures, how long without success and the likely reason (refused credential, deleted channel, destination down), with the path to fix it on screen.

Notes: read-only. Changing the credential, turning back on, resending or removing happens in Settings › Integrations and APIs (Ready-made integrations, Webhooks). An app's credential and a webhook's full URL never come back in the answer.

#77. A package arrived for Acme

For whom: the team (owner, admin, moderator or finance).

Request:

A package from Staples arrived for Acme, at the front desk.

Tools, in order:

Result: the parcel in Waiting for pickup, with the Company badge in the queue. Each current Acme employee with access to the space gets the e-mail (or only the company's admins, if it chose so) and sees the package in My parcels, as "For Acme"; any of them picks it up.

Notes: to notify only the admins, ask "At Acme, notify only the admins when a parcel arrives" (update_company with parcel_notice_admins_only: true). See Parcels for a company.

#78. An event satisfaction survey

For whom: owner or admin.

Request:

Create an "Event survey" space, with a single survey, only for people who bought a ticket, and build the event satisfaction survey in it from the feedback template, anonymous, with the public link on and a deadline of Sunday. In the Content section, add "The length of the talks was…" with Too short, Just right and Too long. Show it to me before opening. Once it is open, send me the link.

Tools, in order:

Result: the survey open, in four steps; whoever bought a ticket gets the e-mail invitation, and the public address (clube.memberfy.net/s/…) takes the survey to attendees without an account.

Notes: opening asks to confirm, because it sends the e-mail invitation; the recipe shows the draft first. Closing before the deadline (close_survey) asks too. In Claude, the Run a survey recipe builds this request. See Surveys.

#79. Upload a batch of photos to the gallery

For whom: anyone who can post in the gallery.

Request:

Upload these photos to the Meetup 2026 gallery with the title "APICON Rio": https://…/1.jpg, https://…/2.jpg, https://…/3.jpg

Tools, in order:

Result: the photos in the gallery, with the title, and the list of what went in and what failed, with the reason. In a gallery with approval, the photos wait for moderation.

Notes: more than 20 photos go in several calls. A large photo goes by link (up to 50 MB); files sent directly share the call's 10 MB. See add_gallery_images.

#80. Review my team's development plans

For: someone's direct leader (any role), the owner or the admin. In Claude, it's in the menu as Review my team's development plans.

Request:

Review my team's development plans: show me the ones waiting for my approval, who has no plan and the overdue actions.

Tools, in order:

Result: each waiting plan approved or returned with your note, and the list of who still has no plan and of the overdue actions. See Development Plan.

Notes: the indirect leader sees the whole team, but only the direct leader (or the owner or the admin) decides. To create a plan for someone without one: "Create a development plan for Bruno, from 11/01 to 04/30", with create_development_plan (dry_run shows first who gets the e-mail).

#81. Set up time tracking

For: owner or admin. In Claude, it's in the menu as Set up time tracking.

Request:

Set up time tracking for my team: create the Time tracking space, register the company as the employer and register Carla and Bruno as employees.

Tools, in order:

Result: the time tracking space linked to the establishment and the people registered, ready to clock in. See Time Tracking.

Notes: the assistant never makes up a CPF: it asks for each person's. It doesn't clock in for anyone either; each person clocks in themselves in the app.

#82. Close the time tracking month

For: the time tracking management: owner, admin or finance. In Claude, it's in the menu as Close the time tracking month.

Request:

Close September in time tracking: decide the pending adjustments with me, show me the totals and export the CSV.

Tools, in order:

Result: the month closed, with the totals frozen, each employee notified to acknowledge and the CSV for payroll. See Time Tracking.

Notes: months close in order and don't close with a pending adjustment. Adjustments for other people's direct reports belong to their direct leader: the assistant points out which ones are still waiting. Only the owner or the admin reopens, with the reason (reopen_timesheet_month).

#83. Open the PDI cycle and follow the adhesion

For: owner or admin. The adhesion, also finance and each leader, about their own team.

Request:

Open the 2027 PDI cycle for everyone: sending by 11/30, approval by 12/15, with reminders 7 days and 1 day before. Show me first how it looks. Then tell me who has already sent.

Tools, in order:

Result: the cycle open at the top of the development plan space, with the deadlines, and the reminders set for the chosen days. See Development Plan › The company cycle.

Notes: opening sends no e-mail right away; the reminders go out on the chosen days, in the Development plan category, and nobody gets two on the same day. Closing (close_development_cycle) asks to confirm and can't be undone.

#84. Download the feedback numbers as CSV

For: owner or admin.

Request:

Give me October's feedback numbers for the Sales group as CSV.

Tools, in order:

Result: the CSV with the totals, the adoption and the requests of the period and group, numbers only. See Feedback › Export the numbers.

Notes: Excel (.xlsx) stays in the app, under Download Excel. Counts of 1 and 2 show as "< 3"; with a group, there's no by-theme block.

#85. Set the radius for clocking in

For: owner or admin.

Request:

In the Time tracking space, only accept punches within 200 m of the office (latitude -23.5614, longitude -46.6559). Anyone outside or without a location can't punch.

Tools, in order:

Result: the radius active on the space; outside it, or without a location, the punch is refused and the attempt is recorded. See Time Tracking › Allowed radius.

Notes: the assistant needs the latitude and longitude; in the app, the address search or Use my location fills in the place. To only flag, use FLAG mode. Removing the radius (remove_time_tracking_geofence) asks to confirm. The rule is the company's, and the location comes from the device of whoever punches.

#86. See my unread messages

For whom: any role (only your own conversations).

Request:

Do I have unread messages? Show me what Ana wrote.

Tools, in order:

Result: a summary of the conversations with unread messages and the text of the one you asked for. See Messages.

Notes: reading through the assistant does not mark it read; only step 4 does, and Ana only sees "Seen" if both people turned on Read receipts. The assistant does not read other people's conversations, not even with the owner role.

#87. Write to someone

For whom: any role.

Request:

Write to Ana: I'll be at the meeting at 3 pm.

Tools, in order:

Result: the message in the conversation with Ana (opened now if it did not exist); she gets it instantly or, if she is available and out of the app, an e-mail without the text. See Messages.

Notes: a new conversation only with someone who is Available to chat, with no block and within the community's rule on who can start; replying to an existing conversation is always allowed. If there are two Anas, the assistant asks which one. To see who is online, list_chat_online_members (only if you are available too).

#88. See who asked to connect and accept

For whom: any role, in a community with Add first.

Request:

Who asked to connect with me? Accept Bruno's request.

Tools, in order:

Result: you and Bruno connected: he gets the notification that you accepted, and both can chat and see each other's full profile. See Messages › Add first.

Notes: to decline, decline_chat_connection: Bruno is not told and keeps seeing the request as sent. The same requests show in list_notifications (type chat.connectionRequested). If there are two Brunos, the assistant asks which one.

#89. Build a form and follow up on the submissions

For whom: any role that can create in the Forms space (the space's Who can post). Opening to visitors and Save as member, only the team.

Request:

Create a "Request a demo" form in the Forms space, open to anyone with the link, with name, e-mail, phone, company, job title and "How many people in your community?" (single choice: up to 100, 100 to 1,000, more than 1,000). Save whoever submits as a member and make me the responsible. Show it to me before publishing and give me the link.

Tools, in order:

Result: the form open at clube.memberfy.net/f/…, with the required consent (open to visitors); each submission reaches the responsibles by e-mail, invites the person to the community with the "Request a demo" tag and shows up in the submissions list. See Forms.

Notes: in Claude, the Collect with a form recipe builds this request. Deleting the form (delete_form) or a submission (delete_form_submission) asks to confirm. export_form_submissions_csv returns the same CSV as the app.

#90. A staff-only announcements channel

For whom: an owner or admin who wants a place for announcements that everyone reads and only the staff writes in.

Request:

Create a staff-only announcements channel in the Community section, called "announcements". Then send the first message: "Welcome to #announcements! The staff posts the week's notes here." Show me before sending.

Tools, in order:

Result: the #announcements channel in the menu, with the first message. Members read and react and see "Only people with permission write in this channel. You can read and react to messages." See Channel.

Notes: for only admins to write, can_create: "admins". The message doesn't e-mail everyone: only whoever is mentioned gets a notice.

#91. Check for a similar topic before creating one

For whom: any role that can propose topics on the board (the space's Who can post).

Request:

On the Suggestions board, check whether there's already a topic similar to "Dark mode in the app". If there is, vote for it; if not, create the topic with the description "I use the app at night and the white screen strains my eyes." Show me before creating.

Tools, in order:

Result: your vote on the existing topic, or the new topic on the board, already with your vote (or awaiting approval, if the board has prior approval). See Upvote.

Notes: the staff later merges whatever slips through, with merge_upvote_topics, which can't be undone. The limit is 5 topics a day.

#92. Log the 1:1 you just had

For whom: any role, with their direct leader or a direct report in the org chart.

Request:

Log the 1:1 I just had with Ana: we talked about the onboarding project and the December vacation. Shared note: "Ana wants to lead the next onboarding." Agreement: she sends the plan by Friday. Show me before saving.

Tools, in order:

Result: today's 1:1, done, in your shared history (Your 1:1s with Ana), with the topics, the note and the open agreement; Ana gets the notice in the bell. See 1:1.

Notes: no e-mail goes out. To change the date later, update_one_on_one_log; to delete, delete_one_on_one_log (open agreements stay). A private note shows in the summary only as "included".

#93. Stop a workflow, or just pause it

For: owner or admin.

Request:

The welcome workflow is sending the wrong e-mail. How many people are on the path right now? I want to stop everything and cancel what is under way. Show me first.

Tools, in order:

Result: no one new enters and the runs under way are canceled; the workflow stays paused and can be turned on again. See Workflows.

Notes: to fix something and carry on with the same people, ask to pause (pause_workflow): each person freezes where they are and continues when you resume.

#94. Automate a rule with a workflow

For: owner or admin (the team can ask for the suggestion, without saving).

Request:

I want whoever buys the Leadership course to get 7 days of access to the mentoring and a DM from me. Build the workflow, simulate it with Maria and show me before turning it on.

Tools, in order:

Result: the workflow is on and every purchase of the course gives 7 courtesy days in the mentoring, with your DM. See Workflows.

Notes: the assistant only uses actions your role allows: an admin cannot build a workflow that makes someone an admin. In Claude, the Automate a rule with a workflow recipe already takes this path.

#95. Put the community on your custom domain

For: owner or admin.

Request:

I want the community at community.papodesysadmin.org, without losing the Memberfy address. Tell me the record to create in DNS and let me know when it's live.

Tools, in order:

Result: the domain shows up in Settings › Address and domain › Custom domain, in the steps up to Active. When it becomes active, the community opens on both addresses, and links and emails start using the custom domain; the owner gets an email. See Custom domain.

Notes: with your DNS provider's proxy on, the certificate isn't issued: the assistant warns you. To change later, ask for the new domain: the old one stays up until the new one becomes active.

#96. Approve the join requests

For: owner or admin.

Request:

Who asked to join the community? Approve the people working in infrastructure and reject the rest with the reason "the community is only for people working in the field".

Tools, in order:

Result: the Members › Pending queue is empty; the approved people show up in Members and fire the New community member workflows with the Came from approval source. See Sign-up and access.

Notes: to switch the mode on from the conversation, ask "Put the community's sign-up on with approval" (update_community_settings with signup_mode). Rejected people get the e-mail with the reason and can ask again after 30 days.

#97. Ask for access to a padlocked area

For: any member.

Request:

Show me the events in the Mentoring space. If I don't have access, ask the team to let me in.

Tools, in order:

Result: the person on the team gets the request in the chat, just as if you had clicked Talk to the team on the space's screen. See Visibility and access.

Notes: with can_contact_team: false (chat off, or nobody on the team available), the assistant gives the reason and doesn't call contact_team. When the space is unlocked by a plan or a product, the way in is to subscribe or buy, not to talk to the team.

#98. List the posts with a tag

For: any member.

Request:

List the posts tagged #jobs in the Community space and tell me which ones are remote jobs.

Tools, in order:

Result: the same list the app shows when you click #jobs in the space, with Showing only #jobs × at the top. See Clickable tags.

Notes: Jobs, jobs and #jóbs give the same result. Each person sees only the posts from spaces they can open. To tag posts, ask "Add the tag jobs to this post" (update_post with tags, which replaces the whole list).

#99. Record the SMS consent from the meetup form

For: owner or admin.

Request:

Record that Maria and João agreed to receive SMS notices on the October meetup sign-up form. João's phone is +1 415 555 0188.

Tools, in order:

Result: on each person's profile, "SMS (notices): consented on 10/28, origin declared by the team", and a line in the community log with who declared it, when and how. João's phone can receive SMS right away (sendable: true) without being verified (phone_verified: false); if he changes his number later, the new one does not inherit the declaration. See Consent declared by the team.

Notes: the assistant only calls the tool when you say the community collected the consent; the responsibility for the declaration is the community's. Anyone who left SMS or withdrew consent comes back as withdrawn, and nothing is recorded. For a large list, or for people who aren't members yet, use the spreadsheet import with the sms_consent column and the attestation.

#100. E-mail a post to the people who can read it

For: owner or admin (moderator and finance create the draft but do not send).

Request:

Turn the article "How to close your first client" into an e-mail campaign for the people who can access it. Tell me how many people receive it, send me a test and schedule it for tomorrow at 9 a.m.

Tools, in order:

Result: the campaign scheduled in Campaigns, with the audience computed at send time: whoever subscribed by then receives it, whoever canceled stays out.

Notes: a post that is a draft, private or pending in moderation does not become a campaign. If you change the audience with update_campaign, the whole text may reach people who cannot access the article. See Send a post by e-mail.

#101. Make my page public

For whom: any role (it's your own page).

Request:

Make my page public, except my experience, and add that I work at Acme. Then send me the link.

Tools, in order:

Result: your page opens without signing in, with name, photo, cover, job title, company, bio, links, country, languages and activity; only members see the experience. It isn't indexed by search engines.

Notes: with public pages off, the assistant warns that the most open level is Members; the owner or admin turns them on (update_community_settings with public_member_pages: true). A section the community limited stays at the limit. Signup fields are never public. See Your profile.

#102. What's trending?

For whom: any role.

Request:

What's trending in the community this week?

Tools, in order:

Result: the list of what's moving the community, with title and author, only from what you can open.

Notes: a comment weighs twice a reaction, and the author's own don't count. See Side column.

#103. What are the upcoming events?

For whom: any role.

Request:

What are the upcoming events? Say I'm going to the first one.

Tools, in order:

Result: the upcoming events you can open, with date and time, and your attendance marked on the first.

Notes: the list is the same as the Feed's side column: a canceled or draft event, or one from a space you don't open, is left out. See Events.

#104. Show new members in the Feed's side column

For whom: owner or admin.

Request:

Show the new members and the leaderboard in the side column of the main Feed.

Tools, in order:

Result: that Feed's side column starts showing New members (who joined in the last 30 days) and Leaderboard (with gamification on). Visitors see neither.

Notes: it applies only to that Feed. feed_widgets: null goes back to the default. See Turn the side column widgets on and off.

#105. Book a Networking conversation

For whom: any role that is in the program.

Request:

In the Mentoring Networking space, find someone in product with a free time this week and book 30 minutes for me to talk about a career change.

Tools, in order:

Result: the confirmed session (or the request, if the person accepts first), with the calendar invite for both. No credits are used.

Notes: a taken time brings the next free ones; a program rule (weekly limit, limit with the same person, notice) comes back explained, and the assistant doesn't retry the same way. In Claude, this recipe is in the menu as Find someone and book a session. See Book a session.

#106. Start mentoring

For whom: any role the program accepts as a mentor.

Request:

I want to be a mentor in the Mentoring space: I offer résumé reviews and conversations about leadership. I'm available Tuesdays and Thursdays, 6 to 8 pm, in 30-minute sessions.

Tools, in order:

Result: your profile in Explore (or the request waiting for the team), with the times and session types ready for whoever wants to book.

Notes: while the request is under review, your times only show after approval. To get each request before it's confirmed, ask for requires_approval: true on the type. See For those who offer sessions.

#107. Reschedule or cancel a session

For whom: either side of the session.

Request:

My Thursday Networking session won't work: move it to next Tuesday at the same time. If that's not possible, cancel it.

Tools, in order:

Result: the other person gets the rescheduling (or the cancellation) by e-mail, with the calendar updated.

Notes: rescheduling and canceling are the Scheduling tools, with no credits in Networking. See My sessions.

#108. Decide the program's requests

For whom: owner or admin.

Request:

Show who asked to be a mentor in the Mentoring space and approve those who already offer something concrete; decline the others explaining that they need to describe what they offer.

Tools, in order:

Result: the approved people show in Explore; the declined ones get the reason by e-mail and can ask again.

Notes: the moderator doesn't decide requests; they only hide reviews. See Approve or decline.

#109. Set me to Busy

For: any role (your own status only).

Request:

Set me to Busy in the chat until I ask to switch back.

Tools, in order:

Result: the red dot on your photo and "busy" for whoever sees you in People. Messages and e-mails keep arriving, without sound and without the window popping open. See Your chat status.

Notes: no confirmation. To switch back, "make me available again" (status: "available"); to stop new conversations, ask for Unavailable (status: "unavailable"). Away cannot be chosen: it shows up by itself after 10 minutes without activity.

#110. Who is online and who is busy?

For: any role (only for someone who is available or busy).

Request:

Who is online in the chat right now? Separate who is busy or away.

Tools, in order:

Result: the list in three groups: available, busy and away. See Messages.

Notes: someone busy or away still gets the message and the e-mail; they may just answer later. Someone unavailable never shows up, nor anyone who blocked you or whom you blocked.

#111. Change my plan and include an add-on

For: any role, on your own subscription (a company admin, also on the company's).

Request:

Switch my plan to Growth monthly and include the Group mentoring add-on.

Tools, in order:

Result: for someone on a R$ 49 a month plan, 15 days from renewal, the assistant shows the summary first: "Takes effect now. Today: Growth (plan difference) R$ 40.00 + Group mentoring R$ 64.50, prorated to 15 days; total R$ 104.50 on the Visa ending in 4242. Next charge on 11/20: R$ 258.00. Group mentoring joins with the change." With your yes, the subscription moves to Growth monthly with the add-on, in a single charge. See Change plan.

Notes: with no saved card, the assistant doesn't ask for confirmation: it sends the link to the Change plan page, with Growth monthly and Group mentoring already checked, so you add the card and confirm in the app. On a change left for renewal (another billing interval, or a cheaper plan), the add-on joins at renewal, with no charge today. Repeating the same yes never charges twice. To pay by PIX or boleto, see the next recipe.

#112. Change my plan and pay by PIX

For: any role, on your own subscription (a company admin, also on the company's).

Request:

Switch my plan to Growth and pay by PIX.

Tools, in order:

Result: the assistant shows the summary, with the charge now by PIX and the change taking effect "once the payment is confirmed". With your yes, it hands back the PIX copy-and-paste code and the QR code, with its expiry: "The plan only changes once this payment is confirmed (pay by 10/30, 3:30 PM). Nothing has changed yet." Once the PIX is paid, the subscription moves to Growth. See Change plan › Payment.

Notes: with payment_method: "BOLETO", the answer carries the boleto link and barcode line; boleto only with more than 4 days to the renewal. A change left for renewal (another billing interval, a cheaper plan) charges nothing now and needs no payment method. Until the PIX is paid, another change is refused, with the details of the payment that is waiting; if the subscription changes before the payment, the amount is refunded.

#113. Open the veterans' room from level 5

For whom: owner and admin, with gamification on.

Request:

Make the Veterans' Room only for people at level 5 or above.

Tools, in order:

Result: whoever is at level 5 or above gets in at once; whoever is below sees the room with a padlock, the level and what is left. Whoever reaches the level later gets in on their own with a bell notice; whoever drops loses access on the next visit. See Visibility and access.

Notes: with gamification off, the level opens nothing. To remove the rule, min_level: null. A level that opens the room cannot be removed from the ladder while it is there.

#114. Build a welcome journey with badges

For whom: owner and admin, with gamification on.

Request:

Create a welcome journey: the First Post badge for whoever posts in Introduce yourself, Conversationalist for 10 comments in the month and Veteran for whoever has been in the community 30 days and has commented 20 times.

Tools, in order:

Result: the three badges are in the catalog, each with its rule. Counting starts now: whoever posted or commented before does not earn it just for that. Each badge is given at the action that completes the count, with the bell notice and the Achievements e-mail. See Award automatically.

Notes: with gamification off, rules do not award. To avoid comment spamming, set a daily cap on Comment on post (update_ranking_rules with daily_caps): over it, the comment does not count. To open a room for whoever earned Veteran, use update_space_access with badge_ids.

#Tips for asking well

• Say what already exists. "In the courses space that already exists" keeps the assistant from creating another one.
• Ask for drafts. Review in the dashboard, then ask to publish.
• Ask to see it first. For posts and replies, "show me before publishing" makes the assistant stop for your approval.
• Dates with a time zone. "11/15 at 7 p.m., Brasília time" avoids surprises.
• One community per conversation. If you have two connections, turn on only the right one.

#Related

• Tools
• Money and confirmation
• Common problems