Master Framework

Overview
Team Structure
Culture
HR
Developers and QA
Plugs and Growth: viaSocket
Growth : viaSocket
Partnership: viaSocket
Support Team
Agency partners (hold)
Marketing #hold
Tools We Use
MCP
Embed
Webinar
Investor
Custom GPTs
Automation book
AI Prompts that we are using
Automation Challenges with Solutions.
Automation Experts Guidelines
Automation Intern Training.
Automation Incentive Programme
viasocket-departments-criteria
Active Paid Subscriptions
DocStarBuilt with DocStar
  1. /
  2. Support Team

Support Team

28th Oct


  • Why didn’t join on time? 3 PM

  • Why late for screen sharing? Were we not prepared for the meeting time priorly?

  • Feeling and meaning - we are communicating in our reply is imp.

  • Even for first request -> send idea or need -> will go ahead with upvotes from roadmap

  • Close lifetime access type chats -> if pending from customer side

  • If unable to understand any case or needing help -> ensure you learn it later and share learning with team

  • Take agenda then only go to meeting

  • Pending from our side - snooze

  • pending from client, but imp/genuine - snooze

  • if client/case is not imp/genuine - don’t snooze - close

  • chats on guest mode -> send proper reply, wait 15-20 mins, give contact details -> close if no reply received, don’t snooze

  • Genuine client with email ID, not replying in chats -> Send mail > snooze email and close chat with your last reply same as sent on mail

  • Learn MCP.


Was this helpful?
DocStarBuilt with DocStar
Was this helpful?