Screen sharing in customer reception for nonprofits

Screen sharing is a human continuation

The reception should never imply that an AI will inspect a donor’s or beneficiary’s screen. The AI receptionist can provide approved orientation and collect a concise purpose. A human host decides whether screen sharing is useful, what public or approved page to show, and what information should remain private.

Good starting purposes include:

• Find a public giving or event page • Understand a volunteer registration step • Orient a partner to a public program resource • Explain where general community resources are located • Review a grant or sponsor resource at a high level

These are navigation tasks. They do not authorize the host to process a donation, evaluate a beneficiary, interpret a grant agreement, or access private case records. Start with the [Kiguri customer reception](/), review Kiguri guides, and verify current plan details at Kiguri pricing before publishing them.

Collect context before opening a screen

Ask for name, organization or program context, purpose, and a short description. If a visitor names an event or public page, include that context in the handoff. Do not ask the visitor to paste passwords, payment information, health information, case records, identity documents, or private beneficiary circumstances into general chat.

If the visitor needs help with safeguarding, crisis response, accessibility, legal, privacy, or urgent welfare concerns, direct them to the nonprofit’s approved human or emergency process. Screen sharing is not a substitute for emergency services, secure case management, or identity verification. The host should state the boundary before inviting a visitor to share.

Let the host choose the destination

Presence and roles can guide the handoff. A donor-services role may explain a public giving page. A volunteer coordinator may orient someone to an event resource. A program team may choose another channel for a beneficiary matter. If no suitable host is available, keep the inquiry in a response queue with an honest message.

When a host accepts, chat may be enough. Browser phone or video can add context; screen sharing is appropriate only when the host has a clear purpose and the visitor understands what will be visible. A private room can provide a focused setting, but it is not proof of donor or beneficiary privacy, security, or regulatory compliance.

The host should avoid displaying other donors’ names, payment details, beneficiary records, messages, schedules, or internal case notes. Ask the visitor to close unrelated windows and share only the public or approved page needed for orientation. Follow the nonprofit’s policies for privacy, safeguarding, access, retention, and sensitive information.

Design the first minute of a screen-sharing handoff

An explicit opening keeps the conversation bounded:

1. Confirm the visitor’s purpose and the page or resource they want to understand. 2. Explain that screen sharing is optional and limited to that topic. 3. Ask the visitor to close private tabs and avoid showing credentials or case details. 4. Choose the human host and channel. 5. End the share when orientation is complete and state the next human step.

This sequence does not guarantee a donation, grant, beneficiary service, or organizational outcome. It gives the host and visitor a shared expectation. If the request moves into case management, crisis response, or an authorized decision, stop sharing and use the nonprofit’s approved process.

Use approved orientation, not improvised advice

The AI receptionist and host may explain where a public page is located, which purpose to choose, and who owns follow-up. Avoid improvising tax, legal, grant, medical, or safeguarding advice during a screen share. If the visitor asks a question outside the approved answer set, capture it and route it to an authorized person.

Do not claim to have submitted a donation, verified a beneficiary, contacted a partner agency, opened a case, or changed an event registration unless that action happened in the nonprofit’s own process. End the share when the visitor needs a secure upload, identity check, or confidential record review.

Prepare staff and visitors

Train hosts on the purpose and boundary of screen sharing. Provide a short checklist for opening, closing, and handling sensitive information. Test with a donor, volunteer, beneficiary-facing partner, grantmaker, event attendee, and after-hours visitor. Ask whether each person understood what would be shown and what the next step would be.

Review a sample of handoffs for accidental exposure, unsupported promises, repeated questions, and visitors who believed the host had made a beneficiary or funding decision. Update approved answers and queue messages from those observations. Keep a register with host roles, screen-sharing purposes, public link placements, queue owner, and review dates.

Internal usage counts may inform staffing, but they do not prove fundraising, beneficiary, volunteer, security, privacy, compliance, or organizational outcomes. Publish only claims the nonprofit can define and verify.

Keep the host checklist with the donor or program-services handbook. Before a campaign, community event, or volunteer period, confirm each purpose has a human owner, office-hours wording is accurate, the queue has a reviewer, and screen-sharing hosts know the sensitive-information boundary. Ask someone unfamiliar with internal program terms to test the reception. Their questions can reveal labels that make sense to staff but not to a donor or community visitor.

Review it after staff rotations or a new safeguarding procedure and before major events. Record the checklist owner, review date, and approved public wording so temporary hosts can explain the boundary consistently.

For rotating teams, name a backup host and a queue reviewer. If a visitor waits beyond office hours, the queue message should describe the actual next step and avoid implying that a donation, case decision, or urgent response has already occurred.

FAQ

Can the AI screen-share with a beneficiary?

No. A human host chooses whether screen sharing is useful after the reception collects approved context.

What should a visitor close before sharing?

Close unrelated tabs and windows. Do not display credentials, payment information, health details, case records, identity documents, or private beneficiary circumstances.

Can screen sharing handle a crisis or safeguarding concern?

No. Provide approved orientation and direct urgent matters to the nonprofit’s established human or emergency channel. The AI should not assess risk or claim a case is resolved.

What if no host is available?

Keep the inquiry in a response queue and explain the actual follow-up. Do not promise immediate help, a donation result, beneficiary service, or an SLA.

Does a private room guarantee donor or beneficiary privacy?

No. It is a conversation destination. Follow the nonprofit’s own policies for privacy, access, retention, safeguarding, and regulated work.

Sources and further reading

• [Kiguri customer reception](/) • Kiguri map preview • Kiguri pricing and plan overview • Kiguri guides

Sources and further reading

Kiguri product overview, Kiguri pricing, security information, and Kiguri guides.