Lansenger Collaboration
Daily work involves a lot of small, fragmented Lansenger operations: send a notice, look up a contact, create a schedule, see what was discussed in a group. None of these is hard on its own, but frequently switching apps disrupts your workflow. With LanMate, you can do it all in a single sentence.
Skills Used
- Built-in skills (installed with LanMate, ready out of the box): Lansenger integration (lanmate-lansenger) — messaging, contacts, schedules, and group chat records all come from it
Pain Points
- App switching: while writing a document, you still have to switch to Lansenger to send notices and look up information
- Manual group notifications: copying and pasting into groups one by one
- Finding people and checking schedules means digging through the address book: name → department → contact info, layer by layer
- Too much group chat information to keep up with: hundreds of messages with no time to read them one by one
- Meeting schedules require notifying each participant individually: after creating a schedule, you still have to notify everyone separately
Recommended Workflow
Describe your need in natural language → LanMate automatically calls the corresponding Lansenger capability to execute → for write operations, confirm before executing → the result is fed back in the conversation.
When calling Lansenger capabilities, LanMate follows a “read before write” principle: it retrieves data first (look up contacts, check schedules), then performs writes (send messages, create schedules), and asks for your confirmation before any write operation.
Prompt Examples
Scenario 1: Group Notification
Send a notice to the "Project Review Group":
Tomorrow at 3:00 PM in the third-floor multi-function hall, there will be a project review meeting.
Each module lead should prepare a progress report — 10 minutes per person.Scenario 2: Look Up a Contact
Help me look up Zhang San's contact info — which department is he in?LanMate searches the Lansenger address book and returns the name, department, title, phone number, and other information.
Scenario 3: Create a Schedule and Notify Participants
Help me create a schedule:
- Title: V0.4.0 Version Review Meeting
- Time: Tomorrow 2:00 PM to 4:00 PM
- Participants: Zhang San, Li Si, Wang Wu
- Location: Third-floor Meeting Room A
Notify all participants after creating it.LanMate first looks up the participants’ address book information to get their staffIds, creates the schedule, and then automatically sends notifications.
Scenario 4: Group Chat Summary
Pull the chat history from the "Project Group" for the last three days,
and organize the discussion highlights and action items.
Keep the summary under 500 words.If the group chat has a lot of messages, LanMate automatically pulls them in batches and compiles a summary.
Scenario 5: View This Week’s Schedule
Show me what schedule I still have this week.Acceptance Criteria
- Messages are sent successfully, to the correct target group or contact
- Contact information is accurate, including department and contact details
- Schedules are created successfully, and participants receive notifications
- The group chat summary covers the key discussions and action items within the specified time range
- Schedule query results are complete, with no omissions
Common Mistakes
| Common Mistake | Why It Happens | Better Practice |
|---|---|---|
| Not stating the target group name | Assuming LanMate knows who you want to send to | State the group name explicitly, e.g., “Project Review Group” rather than “send to the group” |
| Ambiguous time expressions | “Tomorrow afternoon” can be ambiguous | Give specific dates and times whenever possible, e.g., “August 15, 14:00-16:00” |
| Executing write operations without confirmation | Rushing to finish | Confirm the content and recipients before sending messages or creating schedules |
| Not specifying a time range for group chat summaries | “Recent messages” is vague | Specify a clear time range, e.g., “the last three days” or “this week” |
| Confusing bot and assistant identities | Not understanding Lansenger’s dual-identity mechanism | You don’t need to worry about identity details — LanMate chooses automatically; but know that the bot can only send messages to groups it’s in |
Tips
- Group notifications: Group messages can be sent as either the assistant identity or the bot identity, and LanMate chooses automatically: as the assistant identity, the message goes out in your name and recipients see it as coming from you; as the bot identity, it can only be sent to groups the bot is in. A personal bot can only be invited into a group by you (its creator) — to message more groups, invite your bot into the target groups.
- Direct-message notifications: Sent as the assistant identity through your Lansenger account — the recipient sees the message as coming from you. LanMate can also DM you (the owner) as the bot identity — a personal bot can only DM its owner, not anyone else.
- Schedule notifications: After creating a schedule, LanMate notifies participants as the assistant identity; the notification includes the schedule time, location, and participant list.
- Group chat summaries: Summaries are extracted from chat records. Groups for which message records cannot be retrieved cannot generate summaries.