
Closed
Posted
Paid on delivery
Brief: Teams Customer Chasers → Zendesk Automation Oct 21, 2026 · @Edwin Objective Automatically turn customer chasers posted in Microsoft Teams group chats into tracked, prioritised actions on the matching Zendesk ticket. Agents keep working only from Zendesk; Teams becomes one more signal feeding the operational queue. Today, chasers arrive in Teams and must be spotted, matched and acted on manually. The target behaviour: customer chases in Teams → the right ticket is identified from PNR, ticket number or subject → it is marked as chased → it rises in a dedicated Zendesk view. Architecture Customer chaser in Teams → automation captures message → extracts PNR / ticket no. → searches Zendesk → matches ticket → updates it via Zendesk API → native Zendesk trigger → Customer Chasers view → agent action. • Why not the standard Zendesk for Teams app: it lets agents view, create and update tickets in Teams, but does not auto-match chasers or reprioritise tickets. • Division of labour: the automation performs the external Teams → Zendesk update; native Zendesk triggers handle routing and priority afterwards. Zendesk warns against triggers calling webhooks back into the same ticket (race conditions). • Message capture: every new customer message in the relevant Teams group chats must be captured in near real time, through a dedicated operations/service Teams account that is a member of every customer chat. • Identity: OAuth credentials on a dedicated integration identity for production, never personal credentials. Zendesk setup (before building the flow) Custom field Type Purpose Teams Chaser Checkbox Flags tickets chased on Teams Teams Chaser Count Number Chaser events received Last Teams Chaser Date/time Latest chase; drives duplicate suppression Teams Match Status Dropdown Auto Matched / Manual Match / Unmatched PNR Text Matching key (confirm it already exists) Tags: teams_chaser (matched), teams_unmatched_chaser (exceptions). Add tags additively so existing tags are not overwritten. Views: • Customer Chasers — Teams Chaser = Yes. Columns: Ticket ID, Subject, PNR, Status, Assignee, Chaser Count, Last Chaser. Grouped 3+ chasers, then 1–2, then normal queue; normal SLA order within each. • Unmatched Teams Chasers — tag teams_unmatched_chaser. The safety net. Automation requirements For every new customer message, the automation must: 1. Capture the message from the customer Teams group chat as it arrives. 2. Clean it to plain text (strip Teams HTML formatting). 3. Extract the PNR: the 6 characters after PNR:, spaces removed (e.g. PNR: ENIPEC → ENIPEC). Version 1 handles explicit PNR: only. 4. Extract the ticket number after TKTN: (e.g. 978-7493167546). Keep multi-ticket strings such as 160-7363702923/21/22/24 whole for now. 5. Retain the full message text for subject/request-type matching. 6. Search Zendesk tickets for the PNR (Search API, type:ticket <PNR>). 7. Evaluate the results (0, 1 or 2+ plausible tickets) against the matching rules below. 8. Update the matched ticket via the Zendesk API: internal note ("public": false — never emailed to the customer), Teams Chaser = Yes, Chaser Count + 1, Last Teams Chaser = now, Match Status = Auto Matched, tag teams_chaser. 9. Hand over to Zendesk: a native trigger surfaces the ticket in Customer Chasers. Example note: CUSTOMER CHASER RECEIVED VIA TEAMS — PNR: ABLSJB — Customer message: Re:[Voyzant] (TIANTAI) PNR:ABLSJB, TKTN:978-7493167546, Inquiry of name correction. Matching rules Principle: when uncertain, don't guess. Key priority: Zendesk ticket # → PNR → ticket number (TKTN) → subject/request type. Situation Action PNR + exact/near-exact subject Auto match PNR + TKTN + request type Auto match PNR + TKTN, one plausible result Auto match PNR + request type, one result Auto match PNR only, multiple tickets Unmatched No PNR Unmatched Multiple plausible results Unmatched Example: PNR KCAQDG returns #18201 Refund, #18244 Involuntary Reissue, #18301 Name Correction. The chaser reads "Inquiry Involuntary Reissue" with TKTN 160-7363702923, so #18244 is selected. To raise match rates, ask customers to use a standard subject: 1589052 | PNR ABC123 | Refund Pending. Unmatched handling No confident match creates an exception ticket (POST /api/v2/tickets), so no chaser is lost. • Retry first: Zendesk search indexing can lag a few minutes. On zero results, wait 2–3 minutes and search once more before raising an exception. • Exception ticket: subject UNMATCHED TEAMS CHASER – <PNR>; internal details list PNR, TKTN, customer message, possible matches (e.g. #18201, #18244, #18301), reason, and "ACTION REQUIRED: identify the correct ticket and apply the chaser". Tag teams_unmatched_chaser. • Routing trigger: tag teams_unmatched_chaser → Group = B2B Operations / Floor Support, Priority = High. One named owner per shift. • Exception SLA: 0–5 min Match Required · 5–10 min Match Overdue · 10+ min Supervisor Alert. • Teams alert: if still unhandled, the automation posts to an internal ops group chat: PNR, customer, minutes waiting, number of possible tickets, link to the Unmatched queue. Escalation, duplicates and limitations Escalation tiers (Zendesk triggers on Chaser Count; do not set Urgent on every message): Chaser count Action 1 Tag teams_chaser 2 Appears in Customer Chasers – Priority 3 Priority = High + notify supervisor 4+ Operational escalation Duplicate suppression: if Last Teams Chaser on the same ticket is under 10 minutes old, add the note only; otherwise increment the count. Four messages in three minutes = one chaser event, each still recorded. Limitations: • Capture must cover the way customers actually chase: group chats, channel replies, shared channels and 1:1 chats may each need separate handling. • Capture only works for chats the service account belongs to. • Search index lag (see retry above). Rollout and open decisions No AI is needed for version 1. Build in three phases, proving each on test tickets before moving on. 1. Phase 1 – MVP: capture Teams message → extract PNR → search Zendesk → add internal note. 2. Phase 2 – Prioritisation: multi-ticket matching, chaser count, Zendesk views and escalation tiers. 3. Phase 3 – Safety net: unmatched workflow, search retry, exception SLA, Teams alerts, duplicate suppression. 4. Later: automated Teams acknowledgements to customers (e.g. "Chaser recorded against #1589052 · Status: Pending · Assigned: John · Chaser count: 2"), only once matching is reliable; fallback PNR detection without the PNR: prefix. Open decisions: [ ] Confirm chasers arrive via group chats (vs channels, shared channels or 1:1 chats) [ ] Provision the dedicated Teams service account and add it to all customer chats [ ] Zendesk admin to create fields, tags, views and OAuth credentials [ ] Name the per-shift owner of the Unmatched view [ ] Agree the standard customer subject format
Project ID: 40779915
57 proposals
Remote project
Active 2 days ago
Set your budget and timeframe
Get paid for your work
Outline your proposal
It's free to sign up and bid on jobs
57 freelancers are bidding on average ₹20,635 INR for this job

I understand that you need an automation solution to capture customer chasers from Microsoft Teams and integrate them with Zendesk tickets. My approach will involve setting up a workflow that captures messages in real time, extracts relevant information like PNR and ticket numbers, and updates Zendesk accordingly using its API. I will ensure that the automation is robust, handles errors effectively, and maintains logging for tracking purposes. You will receive a fully functional integration that streamlines your operations between Teams and Zendesk. My work is backed by a 5.0 Freelancer rating and 111 client reviews. Clients have described me as reliable, detail-oriented, responsive, and professional. They've praised my clear communication, quick turnaround, accurate results, and ability to understand requirements and solve difficult problems. One long-term client has worked with me for over three years and highlighted my trustworthiness and willingness to go above and beyond. Could you clarify if there are any specific error handling requirements or logging preferences? Also, do you have an existing setup for the OAuth credentials? Best regards, Hussein
₹25,000 INR in 3 days
5.8
5.8

Trap here is a PNR hitting two open tickets or three chases in a row from one customer: each lands once, in the right view, no double counts. Day 1: fields, tags and both views live in your Zendesk, plus a first chaser from a test chat landing on a ticket for you to check. Day 3: full flow running on the integration identity, unmatched path tested. 1. Can your M365 admin grant app consent for the service account, or is it delegated sign-in only? 2. Roughly how many customer chats and chasers per day? Fields and views can be set up today while you sort the integration login.
₹15,600 INR in 3 days
5.4
5.4

Building automation systems that connect business tools and remove manual work is my core focus, supported by 40+ production deployments. Your Teams-to-Zendesk workflow is a strong match for my automation, Node.js, Python, FastAPI, PostgreSQL and AWS experience, allowing me to create a reliable integration around Teams message capture, Zendesk API updates and production-ready OAuth handling. I can implement the required chaser processing while preserving the safety rules: plain-text extraction, explicit PNR/TKTN parsing, Zendesk search and confidence-based matching, with ambiguous cases routed to an unmatched path rather than guessed. The matched-ticket update can maintain the internal note, checkbox, count, timestamp, status and additive tags, while native Zendesk triggers remain responsible for views and prioritisation. My production-first approach also supports clean deployment and documentation for a dedicated integration identity rather than personal credentials. I would be glad to build this integration as a dependable operational system that gives agents one trusted Zendesk queue for Teams chasers. Choose me to turn the specification into a maintainable automation.
₹12,500 INR in 6 days
3.2
3.2

I can build the flow that takes customer chasers from your Teams group chats and attaches each one to the matching Zendesk ticket as an internal note. The slow part is likely to be getting messages out of Teams, so I would confirm the service account can read each customer chat before anything else. In the order I would work: 1. Confirm the service account can read your customer chats and pull a day of real chaser messages. 2. Check the PNR: and TKTN: extraction against those messages. 3. Search Zendesk by PNR and add the chaser as an internal note on the matched ticket. 4. Run the chain on test tickets before any live ticket is touched. Check the log against three chasers you already know before you release the rest. - 4,000 INR for steps 1 and 2, when the capture log from your real chats is in your hands - 8,500 INR for steps 3 and 4, when a test chaser lands as an internal note on the right ticket The total is 12,500 INR, covering the capture, the PNR and ticket extraction, the Zendesk match and the internal note. I can take this now.
₹12,500 INR in 6 days
2.6
2.6

Hi Edwin, Your brief is clear: chasers land in Teams group chats, agents stay in Zendesk, and the automation sits in between. That is the kind of API bridge we build. How I would do it: - Microsoft Graph change notifications on the chats the service account is a member of, with auto-renewing subscriptions and a catch-up poll so nothing is lost if a notification drops - extract PNR / ticket number / subject with tested patterns, then search Zendesk and pick the match - update the ticket through the Zendesk API: Teams Chaser flag, count, Last Teams Chaser time, Match Status and tags, added additively so existing tags stay - duplicate suppression on Last Teams Chaser, unmatched chasers tagged teams_unmatched_chaser for manual review - your native triggers and the Customer Chasers view do the rest, no webhook back into the same ticket It runs on an Azure Function or any small server you prefer, with OAuth on the dedicated integration identity, never personal credentials. You get the source, a setup guide for the app registration and the Zendesk fields, and a test run on a sample chat. Quick first step: a dry-run that reads one test chat and prints which ticket it would match, so you see the matching logic before anything writes to Zendesk. One question: is the PNR format fixed, or does it vary by airline / GDS? Completed projects on this account are rated 5 out of 5, delivered on time and on budget. Petro Pankov, BotCraft Group
₹15,000 INR in 7 days
2.0
2.0

My background in AI-driven workflow automation, API integrations, and scalable software architecture directly matches this Teams-to-Zendesk integration. With nearly 20 years in software engineering and technology leadership, plus a PhD in Artificial Intelligence and a Bachelor’s degree in Computer Science, I can build a reliable bridge that turns Teams customer chasers into structured Zendesk actions. I have developed customer-support voice and chat agents, workflow automation tools, full-stack SaaS platforms, CRM integrations, data-extraction systems, and backend/API solutions. That experience is highly relevant to capturing Teams messages, cleaning and parsing PNR/TKTN data, applying careful matching logic, updating Zendesk fields and tags without overwriting existing data, and preserving unmatched cases for safe manual handling. My automation and third-party integration skills also support a production design based on dedicated OAuth credentials and Zendesk’s native triggers and views. I would be pleased to deliver this integration with the accuracy, safety, and operational focus your support team needs.
₹12,500 INR in 7 days
1.1
1.1

You've mapped the gap well: the standard Zendesk for Teams app can view and update tickets but never auto-matches a chaser to its ticket. I'd build the flow exactly as you sketched. A dedicated operations Teams account subscribes to the customer group chats through Graph API, each new message is parsed for the PNR or ticket number, Zendesk is searched, and the matched ticket gets the Teams Chaser checkbox, an incremented chaser count, and a Last Teams Chaser timestamp that drives duplicate suppression. Each message produces one Zendesk API update, so your native triggers handle routing and priority without a webhook calling back into the same ticket. Everything runs on a dedicated OAuth integration identity, never personal credentials. I can deliver a working end-to-end flow against your sandbox in 5 days, then tune the field matching on your real chaser wording.
₹27,000 INR in 5 days
0.3
0.3

Hi Edwin, your brief is clear and I agree with the split: the automation only does the external Teams to Zendesk update, native Zendesk triggers handle priority and the view. How I would build it: - Capture: a small service (Azure Function in your tenant) using Microsoft Graph with the dedicated operations account (OAuth, delegated, no personal credentials). It reads new messages from the customer group chats through delta queries every minute, which avoids the protected-API approval that app-only chat subscriptions require, and stores processed message IDs so nothing is handled twice. - Matching: extract PNR, ticket number and subject keywords with tested patterns, search Zendesk (search API on your custom PNR field and ticket ID), and only act on a single confident match; ambiguous or no-match chasers go to a review list instead of guessing. - Update: set the "chased" custom field and tag, increment a chase counter, add an internal note quoting the Teams message with a link. Your native trigger then raises priority and the "Customer Chasers" view picks it up. No webhook back into the same ticket. - Ops: logging, retry on API limits, token refresh, and a short runbook. We build API and webhook automations every day (Stripe, WhatsApp Cloud API, Google Ads API), so the integration side is routine for us. Price: 30,000 INR, 10 days, including testing against real sample chats. Should it run as an Azure Function in your tenant, or do you prefer Power Automate?
₹30,000 INR in 10 days
0.0
0.0

My experience with Zendesk setup and management directly matches your goal of turning Teams chasers into reliable, prioritised ticket actions. I have completed 250+ freelance and remote projects across automation, data workflows, customer support, CRM administration, and business operations, giving me the practical combination needed for this integration. I can support the Zendesk side with the custom fields, tags, views, internal-note updates, chaser counting, match-status handling, and native trigger logic you outlined. My automation experience includes AI-driven workflows with Zapier, while my data management and cleansing background is relevant to extracting plain-text Teams messages, identifying PNR/TKTN values, retaining full message context, and handling matched versus unmatched cases safely. I also understand the importance of additive tag updates, duplicate suppression, non-public notes, and avoiding uncertain ticket matches. My Zendesk skill and broad automation support experience make me a dependable choice for building this workflow with the required safety-net behaviour. I would be glad to take responsibility for delivering the Teams-to-Zendesk integration.
₹25,000 INR in 4 days
0.0
0.0

Hi, I can build a reliable Microsoft Teams → Zendesk automation that captures customer chasers in near real time, extracts PNR and ticket details, and matches messages to the correct Zendesk tickets using your defined rules. The workflow will add internal notes, track chaser counts, update timestamps and tags, and prioritize tickets without overwriting existing tags or sending unnecessary customer emails. I’ll develop this in three phases: message capture and basic matching, ticket prioritization and escalation, then unmatched-message handling with retry logic, duplicate suppression, exception tickets, and Teams alerts. I’ll test each phase using sample messages and Zendesk test tickets, including ambiguous matches and search delays, before production deployment. I’ll also document the required Microsoft Graph permissions, dedicated service-account setup, Zendesk OAuth configuration, and any third-party licensing considerations for a maintainable handover. Best Regards, Mustafa M
₹25,000 INR in 5 days
0.0
0.0

Hi! Your Teams chaser to Zendesk automation (phase 1), working 4 days after the award. You pay us nothing until you've seen it work. Here is what you get: • Every new customer message in your Teams group chats captured as it arrives • PNR: and TKTN: pulled out, Zendesk searched, the right ticket matched • An internal note (never emailed to the customer) plus your Teams Chaser fields and tag • Tested on your test tickets, with the code and a short setup guide handed over Phases 2 and 3 (chaser count, views, unmatched safety net) are quoted after phase 1 works, each with its own preview. Good to know: reading chats needs one-time consent from your Microsoft admin, so we send the exact permission list on day 1. ✅ Included: 3 small changes within 3 weeks after you approve the work, and we fix any bug of ours for free. Our own demo: an e-shop to warehouse order sync that survives duplicates and outages. Price: 12500 INR, 45% off our regular 23200 INR, our introductory price. Question: do chasers reach you only in group chats, or also in channels and 1:1 chats? P.S. Oldrich, the owner, supervises the work and stands behind every result. We use various tools and AI agents to work fast and efficiently.
₹12,500 INR in 4 days
0.0
0.0

Within 48 hours, I will deliver a reviewable Zendesk field/view/trigger blueprint plus matching test cases before completing the live flow. How I will do it 1. Configure Microsoft Graph capture for the operations identity, with validation, retries and message-ID deduplication. 2. Convert Teams HTML to plain text, normalize PNR/TKTN values, and retain the original message as a private Zendesk note. 3. Match tickets by ticket number, PNR and request type/subject; ambiguous results go to Unmatched. 4. Update tickets safely: increment Chaser Count, set timestamp/status, and add tags without replacing existing tags. 5. Prevent duplicate count inflation; use Zendesk triggers only for routing/view prioritisation. What you get - Teams-to-Zendesk automation for PNR: and TKTN: messages - Auto-match, private notes, and field/status/tag updates - Unmatched handling with teams_unmatched_chaser - Customer Chasers and Unmatched Teams Chasers views, plus routing trigger - Test matrix and handover notes Timeline Day 1-2: Blueprint, field IDs, views and test cases Day 3-5: Teams capture, parsing, matching and Zendesk updates Day 6-7: Duplicate/ambiguous testing, trigger validation and handover Price: 12500 INR Delivery: 7 days Do the PNR custom field and its Zendesk field ID already exist? Also, should the integration capture every chat involving the operations account, or is there a defined list/naming rule for customer group chats?
₹12,500 INR in 7 days
0.0
0.0

The project to automate the capture of customer chasers from Microsoft Teams into Zendesk is a great fit for my skills. I see the challenge in making sure that those automated messages capture messages from various chat types—group chats, channel replies, and 1:1 chats—while adhering to the constraints of the service account's membership. And the search index lag in Zendesk can complicate timely updates, but I've dealt with similar issues before by implementing retry logic to make sure no chasers are lost. My approach will focus on building the integration in three phases, starting with the MVP to capture and extract the necessary data, I’ll make sure to handle the PNR extraction and ticket matching efficiently while implementing the escalation tiers and exception handling as outlined. I can go ahead and charge 22499 INR for this project, and I’m ready to get started on this right away. Rajavel Microsoft Teams & Zendesk Integration Specialist
₹22,499 INR in 1 day
0.0
0.0

Hi, you want customer chasers in Teams to find the right Zendesk ticket by PNR, ticket number or subject, mark it chased, and surface it in a Customer Chasers view, with an exceptions queue when the match is not confident. How I would build it: Teams capture, parsing (PNR and TKTN extraction) and Zendesk Search API matching run in n8n or Power Automate, whichever you already license, on a dedicated integration identity with OAuth. The ticket update is an internal note plus your custom fields and tags, added additively. Routing, priority and chaser-count escalation stay in native Zendesk triggers, so nothing calls back into the same ticket. I would follow your three phases, proving each on test tickets. Phase one, INR 12,500 in 4 days: the Zendesk setup (fields, tags, both views, chaser-count triggers) and the main flow for a confident match (capture, extract, search, match, internal note, fields, tags). Phase two: unmatched handling with the retry, exception ticket and SLA triggers. Phase three: the Teams alert, duplicate suppression and channel, shared and 1:1 chat coverage. Phases two and three are priced once phase one works. We have built similar integrations for existing clients, but they are under confidentiality agreements, so I cannot share them. Questions: is there a Zendesk sandbox, and can your Microsoft 365 admin give the service account the Teams permissions? Aakaash
₹12,500 INR in 4 days
0.0
0.0

Hi, Pure Code here, from Saudi Arabia. What matters most in building your PROJECT with 3+ chasers, four messages and a teams alert is data that moves between the systems on its own, without silent failures. I'm a senior full stack developer with 8+ years of experience working with HTML and API Integration. With Zendesk, the real challenge is tokens, rate limits and retries. A common issue: only testing the happy path, so the first expired token or timeout breaks the sync silently. My plan: first, review the API docs, limits and auth flow of Zendesk. Then, build the integration with retries, logging and duplicate checks. Finally, test failures, timeouts and expired tokens before switching it on. I've done integration work in HTML, so I check early for expiring tokens and rate limits. A few questions to better understand the scope: 1. Can one event arrive twice, like a webhook retry? I'd add a duplicate check, so retries never create doubles. 2. Sync one way first, two-way later? I'd recommend one way first, two-way sync needs conflict rules. 3. Who acts on the synced data, staff or customers? Customer-facing data needs faster sync and clearer errors. I can start right away. Happy to go over the details here in chat and suggest the best approach. Looking forward to hearing from you, Pure Code
₹25,000 INR in 7 days
0.0
0.0

Hi Edwin, This is one of the most well-specified briefs I've seen: matching rules, exception handling, escalation tiers, phased rollout. That clarity is exactly what makes this integration buildable, and I'd follow your build order as written. I've spent 10 years building automations that capture customer messages in real time, extract structured data and update downstream systems via API. Recent production work: a debt-collection agent on WhatsApp (AWS, Lambda, SQS, API Gateway, DynamoDB) for a multinational agro company, and web-to-WhatsApp AI funnels for Brazil's largest car dealership group. I also have 5+ years on Blip Desk, a customer-service ticketing platform, so I know the operational side: duplicate suppression, unmatched queues and escalation are where these projects succeed or fail, and your spec already handles them. Version 1 needs no AI, just disciplined engineering: capture via the Teams service account, PNR/TKTN extraction, search retry for index lag, additive tagging. Straightforward work for me. Message me and I'll share a quick outline of the phase 1 approach. Best, Igor Pimenta
₹12,500 INR in 21 days
0.0
0.0

Hello, I have practical experience in automation using Python and Selenium through my internship at Airtel, where I worked on automating site optimization tasks and reducing manual effort by 70%. I can help automate repetitive tasks, improve workflow efficiency, and reduce manual work. I focus on writing reliable automation scripts, understanding project requirements, and delivering work within the agreed timeline. I would be happy to discuss your automation requirements and provide a suitable solution. Thank you for considering my proposal.
₹15,000 INR in 7 days
0.0
0.0

Your agents should see chased tickets in Zendesk without watching Teams or risking incorrect matches. I would capture the agreed group chats, extract PNR/TKTN and request type, match conservatively and add private notes; ambiguous cases go to Unmatched. I have built n8n/Make workflows for agencies, including HubSpot CRM synchronization, and API-based subscriber synchronization for a B2B publisher. Those projects involve similar event matching, retries and reconciliation. 59,000 INR fixed for all three V1 phases: capture/matching; fields, views and escalation tiers; retries, exceptions, 10-minute count suppression and internal Teams alerts. Includes a persistent queue, message-ID deduplication, subscription renewal, tests, deployment in your accounts and handover. Customer acknowledgements remain a later phase. First test message to a test ticket within 48 hours; V1 within 7 days after agreed acceptance cases and dedicated account, admin-approved Graph access and Zendesk OAuth/test access. We confirm chat access and tenant licensing before rollout; hosting/licenses are agreed separately. Acceptance covers unique/ambiguous/missing PNR, delayed indexing, repeat delivery, four messages in three minutes and restart recovery. Notes stay private and existing tags remain. Are the initial conversations group chats in one M365 tenant, with an admin able to approve the integration identity?
₹59,000 INR in 7 days
0.0
0.0

Edwin, the risky part here is capture, not Zendesk: Graph subscriptions on chat messages expire within an hour and need renewing, and reading every chat with application permissions may need Microsoft's protected-API approval, which can take days. I'd file that request on day one so it stays off the critical path. The build would be a small TypeScript service on Graph webhooks, your matching table as unit-tested rules, the search retry as a queued job, and additive tag updates so existing tags survive. Phase 1 should be running on test tickets inside the first week. Would you want it hosted in your own Azure tenant?
₹32,000 INR in 12 days
0.0
0.0

The hard part of this brief is not the Zendesk update but matching each Teams chaser to the right ticket without guessing, and never losing one when the match is uncertain. I would build it in your three phases on test tickets: capture and clean the messages and extract PNR and TKTN, then run the Search API with the retry on zero results and your matching rules, then the internal note, field updates, duplicate suppression and exception tickets. I haven't worked with Zendesk or the Teams API directly, but I implemented multi-provider bulk messaging (Meta WhatsApp API, Infobip, email) with proactive rate limiting and 429 resilience through Pub/Sub's exponential backoff, and I built integrations with new third-party providers. I'd write it in Node.js and TypeScript (NestJS, MongoDB, MySQL, Google Cloud). One question: will the service account already be a member of every customer chat, or should the build also cover channel replies and shared channels?
₹18,000 INR in 14 days
0.0
0.0

Gurgaon, India
Member since Jan 24, 2019
₹12500-37500 INR
$10-30 CAD
$30-250 USD
$250-750 USD
€12-18 EUR / hour
$15-25 USD / hour
₹100-400 INR / hour
$250-750 USD
$2-8 USD / hour
₹600-1500 INR
₹1500-12500 INR
$250-750 USD
$250-750 USD
$10-30 USD
$250-750 USD
₹12500-37500 INR
$15-25 CAD / hour
₹12500-37500 INR
$15-25 USD / hour
$15-25 USD / hour
$750-1500 USD