Walkthrough
Walkthrough: Delegate directory and chat request
A read-only walkthrough, not an interactive demo. In the product: your first message is a request, not a chat: the other delegate's phone shows Accept chat request and nothing flows until they tap it. Two phone panes show both sides, plus a rule that limits networking to ticket-holders. The demo uses forty fictional delegates with interest tags.
A walkthrough, not a live demo. Nothing on this page is interactive. Fictional delegates; replies are scripted. Directory is rules-based, not AI matchmaking. Two panes share state on this page only.
Step by step
- Search the directory. Delegates, All, then search by name, company, designation, city or tag.
- Send a chat request. Your first message becomes a request that waits for acceptance.
- Accept or reject. The other phone shows Accept chat request and Reject.
- Block with limits. Block everywhere, or hide only posts, comments or messages.
What happens on each screen
This is a written walkthrough, not an interactive demo: there is nothing to tap on this page. It describes how the screens behave in the product, using sample data.
Sample data: forty fictional delegates of an exhibition-style conference, each with a company, designation, city and interest tags, plus three scripted replies. Nothing is stored. Two phones sit side by side: Priya on the left, a delegate called Rohan on the right. On Priya's phone, open Delegates and choose All. A search box takes a name, email, phone, company, designation, city or tag, and the list narrows as you type. Open a profile to see company, designation, city and interests. Type a message and send it. It does not open a chat. It sends a chat request, and the phone says You can continue once the receiver accepts your chat request. Look now at Rohan's phone, under My Chats. The request is waiting, with two buttons, Accept chat request and Reject. Accept, and the conversation opens on both phones with a seen state; a short typing indicator shows a scripted reply. The design is consent first: nobody lands in a stranger's inbox. If a conversation turns unwelcome, Rohan can use Block this user. Under Profile, Blocked Users lists the person with a choice of Blocked everywhere, or Limited blocks that hide posts only, comments only or messages only. Unblock reverses it. Below the phones are rule toggles. Switch on Networking for ticket-holders only and a third persona who has no ticket can still browse the directory, but messaging is locked and a Register Now banner appears. There is no AI matchmaking; the directory is rules-based, driven by groups and tags. Next step: read the delegates directory feature page, and see how the APMI conference and the GCOO conclave set up networking.
Questions people ask
Why does the first message need acceptance?
To keep networking consensual. The first message is a chat request, and nothing flows until the other delegate taps Accept chat request.
Can I block someone partially?
Yes. Besides Blocked everywhere, Limited blocks can hide only their posts, only their comments or only their messages. Unblock reverses it.
Can networking be limited to ticket-holders?
Yes. A rule can make messaging ticket-holders only; others can browse but see Register Now where messaging would be.
Does Sociana do AI matchmaking?
Not as a claim. The directory is rules-based, using groups, tags and search, with chat requests for consent.
Seen enough to try it?
We will load a demo with your agenda and your groups, so your team can test it on their own phones.