
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: 40789972
81 proposals
Remote project
Active 11 hours ago
Set your budget and timeframe
Get paid for your work
Outline your proposal
It's free to sign up and bid on jobs
81 freelancers are bidding on average ₹23,043 INR for this job

I will develop an automation solution to capture customer chasers from Microsoft Teams and update Zendesk tickets accordingly. This will involve creating a dedicated operations account in Teams to monitor messages in real-time, extracting relevant information such as PNR and ticket numbers, and using the Zendesk API to update the tickets with the appropriate flags and status. My approach will ensure that the automation runs smoothly, preventing race conditions with native Zendesk triggers while maintaining a clear workflow for your agents. With around 4 years of experience in Python automation and working with REST APIs, I have successfully implemented similar integrations and can provide a self-contained solution with clear setup instructions. I will ensure that the extracted data is validated and logged properly during the process. 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 provide more details on how you envision the matching rules? Are there any specific edge cases I should be aware of? Best regards, Hussein
₹25,000 INR in 5 days
5.8
5.8

Edited or quoted Teams messages re-firing as fresh chases is what inflates counts; we treat them as one event so the view stays honest. Day 1: fields, tags and both views in your Zendesk plus a dry run on a test chat for you to check. Day 3: live on the real chats with a short runbook and exception log. 1. Do we build in a Zendesk sandbox first, or straight in production? 2. Roughly how many customer group chats does the service account sit in? Happy to walk through the exception handling in chat; we can start today.
₹19,575 INR in 3 days
5.4
5.4

Hi, Your brief is clear, and I'd build it in the order it's written: the Zendesk custom fields, tags and the Customer Chasers view first, then the flow. Message capture would use Microsoft Graph change notifications on the chats of the dedicated operations account, with a delta-query backfill so nothing is lost if a notification drops, all running on an OAuth app registration for that integration identity. Each message goes through a parser that extracts PNR and ticket numbers, searches Zendesk and, on a single confident match, updates the ticket via API: Teams Chaser ticked, count incremented, Last Teams Chaser set, tags added additively. Ambiguous or missing matches get the unmatched tag for manual review, the last-chaser timestamp drives duplicate suppression, and native triggers keep handling priority. Would you rather this run on a Power Automate premium licence, or is a small hosted service such as an Azure Function acceptable?
₹16,250 INR in 6 days
4.1
4.1

Hi, Teams chasers matched to the right Zendesk ticket by PNR or TKTN. Matching is the risky part, so anything ambiguous goes to Unmatched, never a guess. How we'd build it: a Graph subscription on the service account's chats, HTML stripped, regex for PNR and TKTN, the Search API, then your rules table. A match gets the private note, the fields and an additive tag. Is the service account already in every chat? We built the agentic call centre for JS Bank. Happy to start on a first milestone. Regards, Digitalizers
₹18,750 INR in 14 days
3.1
3.1

Hello, I can build and deploy your automated Microsoft Teams to Zendesk chaser integration in three robust phases as specified. My approach involves setting up a dedicated integration service account to capture real-time messages from your Teams group chats, processing the text through a deterministic extraction engine (handling explicit PNR and TKTN strings), and querying the Zendesk Search API. I will implement search-index lag retry logic, strict multi-ticket matching rules, duplicate suppression under 10-minute windows, and exception ticket creation tagged with `teams_unmatched_chaser` for your floor support queue. All updates to matched tickets will be injected via private internal notes using OAuth authentication, leaving native Zendesk triggers and views to handle the operational routing and prioritization queue. 1) Which platform or orchestration tool (such as Node.js / Python service hosted on AWS/Azure, or an integration platform like Make/n8n) do you prefer for hosting the automation logic? 2) Have the custom fields (`Teams Chaser`, `Teams Chaser Count`, `Last Teams Chaser`, `Teams Match Status`, `PNR`) already been created in your Zendesk admin environment? Thanks, Bharat
₹35,000 INR in 15 days
2.6
2.6

Hello Edwin Ravi, I can build the MS Teams to Zendesk ticketing automation you require, ensuring seamless capture, extraction, matching, and updating of customer chasers in near real-time. With extensive experience automating workflows and integrating APIs, I will implement the multiple matching rules, handle unmatched cases with retries and exception tickets, and configure Zendesk triggers for escalation and prioritization exactly as detailed. I will develop the solution using robust OAuth authentication on a dedicated integration identity, ensuring secure, stable operation without personal credentials. The solution will cover message capture from Teams group chats and maintain data integrity with duplicate suppression. I understand the phased rollout—starting from MVP extraction and searching, then advanced prioritization and finally unmatched workflows and alerts—and will coordinate closely to validate each phase before progressing. Let’s discuss next steps and timelines so I can deliver a reliable, maintainable automation aligned with your operational goals. I look forward to working with you on this important integration. Best regards, Mayank
₹18,000 INR in 12 days
2.1
2.1

Nearly 20 years across software engineering, AI, and technology leadership make me well suited to build this Teams to Zendesk automation with the reliability your operational workflow requires. I hold a Bachelor’s degree in Computer Science and a PhD in Artificial Intelligence, and as a former CTO I have led end-to-end development of workflow automation tools, SaaS platforms, API integrations, and scalable backend systems. I am ready to apply my automation and integration experience to deliver a dependable bridge between Teams and Zendesk. Choose me to build this carefully around your matching and safety requirements.
₹12,500 INR in 7 days
1.1
1.1

**Available today to build your Teams to Zendesk chaser automation** I am Anand. I build workflow automation that connects chat, forms and support systems, and I can build this exactly as specced. Why not the standard app: agreed, it is for working tickets inside Teams. It does not auto match a chaser to a ticket or reprioritise it, which is the whole point here. Division of labour: my automation will do the external Teams to Zendesk update only. Native Zendesk triggers will then handle routing and priority, avoiding webhook loops back into the same ticket. Message capture and Identity: I will capture new messages in near real time from the relevant group chats using the dedicated operations account you add to every customer chat. For production I will use OAuth on a dedicated integration identity, never personal credentials. Zendesk setup: I will add Teams Chaser, Teams Chaser Count, Last Teams Chaser, Teams Match Status and confirm the existing PNR field. I will add teams_chaser and teams_unmatched_chaser tags additively without overwriting existing tags. Customer Chasers view: Teams Chaser = Yes, with Ticket ID, Subject, PNR, Status, Assignee, Chaser Count and Last Chaser, grouped 3+ chasers, then 1 to 2, then normal queue with SLA order inside each group. Unmatched Teams Chasers view: tickets tagged teams_unmatched_chaser as the safety net for manual handling. For each message I will: 1. Capture it as it arrives. 2. Clean Teams HTML to plain text. 3. Extract the 6 characters after PNR: with spaces removed, explicit PNR: only for v1. 4. Extract the number after TKTN: and keep multi ticket strings like 160-7363702923/21/22/24 whole. 5. Retain the full message text for subject and request type matching. 6. Search Zendesk via Search API for type:ticket plus the PNR. 7. Evaluate 0, 1 or 2+ results against your matching rules. 8. Update the matched ticket via the Zendesk API with the chaser flag, count, timestamp, match status and tags, or route it to unmatched. Recent work: Built a lead intake flow from forms, email and chat into one CRM saving ~15 hrs/week, plus an AI agent handling first-line support replies. Can you share the full matching rules for step 7 and access to a test Teams chat and Zendesk sandbox so I can start today?
₹25,000 INR in 7 days
0.0
0.0

Your objective to automatically turn Microsoft Teams customer chasers into tracked, prioritized actions in Zendesk addresses a key manual bottleneck. The core task is setting up a reliable system to capture customer messages, extract crucial details like PNR or ticket numbers, and update the right Zendesk ticket through its API. This ensures agents focus solely on Zendesk, with Teams acting as a signal. I will build the automation to capture new customer messages from Teams group chats, clean the text, and extract PNR or TKTN details. It will then search Zendesk, apply your specified matching rules, and update the ticket with internal notes, chaser counts, and relevant tags like `teams_chaser`. For unmatched cases, it will create exception tickets with a retry mechanism and appropriate tags (`teams_unmatched_chaser`) to ensure no chaser is lost. I've implemented similar data extraction and update systems, like building an invoice processing engine that extracts details and updates records via APIs with high accuracy. Given the dedicated Teams service account needs to be a member of every customer chat for message capture, how do you plan to manage its enrollment as new customer chats are created? Let's discuss this and how we can get your Teams chaser automation running smoothly.
₹16,000 INR in 8 days
0.0
0.0

Hello, Building reliable third-party API integrations and automation is a core part of my 12+ years as a Full Stack Developer, making me well suited to connect Microsoft Teams customer messages with Zendesk ticket workflows. My experience includes Node.js backend development, REST APIs, database design, authentication, deployment, and ongoing maintenance, directly relevant to capturing Teams messages, cleaning and parsing PNR/TKTN data, applying conservative matching rules, and updating Zendesk through its API. I can also implement additive tags, internal notes, chaser counters and timestamps while preserving existing ticket data, with unmatched or ambiguous cases routed safely for manual handling. My focus on secure, maintainable architecture supports the dedicated production integration identity and dependable near-real-time automation this workflow requires. I would be glad to build this Teams-to-Zendesk automation and deliver a reliable integration that keeps agents focused in Zendesk. Thanks!
₹24,975 INR in 5 days
0.0
0.0

Hello, Designing a reliable Teams-to-Zendesk automation is a strong match for my 10+ years as a full-stack developer, with experience in API development, third-party integrations, scalable architecture, and production-ready business platforms. I can build the automation layer that captures Teams messages, cleans and parses PNR/TKTN data, evaluates matching confidence, and updates the correct Zendesk ticket without making uncertain matches. My background in Node.js backends, REST APIs, authentication, database design, and automation supports the key requirements: dedicated OAuth-based integration credentials, near-real-time message handling, Zendesk Search and ticket APIs, additive tag updates, internal-only notes, counter/date-field updates, and safe handling of unmatched or ambiguous results. I also focus on maintainable, secure code and clear exception paths, which is important for preserving existing Zendesk data and allowing native triggers and views to handle the downstream workflow. I can deliver a robust integration aligned with your matching rules and operational safeguards. Choose me to build this Teams-to-Zendesk automation as a dependable production-ready service. Thanks!
₹24,975 INR in 3 days
0.0
0.0

Hi there, thanks for setting out this project so clearly. I'm just starting out on this platform, so I'd be grateful for the chance to show what I can do. I can move quickly and I'm committed to giving you the best possible service from first contact through handover. The PNR and ticket-number matching stood out to me. Free-text chasers are noisy, so I'd normalise and validate identifiers first, then fall back to subject matching only when there is a single confident hit. Since every message has to be captured through the service account, I'd also build the listener to replay anything missed during an outage. Two suggestions: attach an idempotency key to each Teams message so a retry can never mark a ticket as chased twice, and send unmatched chasers to a small "needs review" view instead of dropping them, so nothing slips through. Quick question: do you already have sample Teams message payloads, or should I plan around Graph API change notifications? Thank you for your time. I look forward to hearing from you.
₹12,500 INR in 7 days
0.0
0.0

Phase 1 — Message capture and MVP matching Capture new messages from the agreed Teams group chats using a dedicated integration identity and supported Microsoft Graph permissions. Strip Teams formatting and extract PNR: and TKTN: values while preserving the complete original message. Search Zendesk using the PNR and add an internal note to a confidently matched test ticket. Verify that notes remain private (public: false) and that existing tags are preserved. Phase 2 — Matching and prioritisation Implement the agreed matching hierarchy using ticket number, PNR, ticket number extracted from the message, and subject/request type. Route ambiguous or insufficiently supported matches to the unmatched workflow instead of updating the wrong ticket. Add the chaser checkbox, count, timestamp, match status, and additive tags. Configure the Customer Chasers view and escalation rules through native Zendesk triggers. Phase 3 — Exceptions and reliability Retry zero-result searches after the specified delay to account for Zendesk indexing. Create exception tickets for unmatched chasers, including the message, extracted identifiers, possible matches, and reason for escalation.
₹25,000 INR in 7 days
0.0
0.0

I'll provide an automation that picks up each customer chaser from your Teams group chats, matches it to the right Zendesk ticket by PNR or ticket number, and marks that ticket as chased, so agents see every chase in one Customer Chasers view without copying anything across by hand. I've spent over 11 years building integrations and automations that move data between business systems. In a previous role I built an integration that saved about 20 staff hours a week. The design here depends on REST APIs, OAuth and webhooks, which I use every day, and it would run on a dedicated integration identity rather than personal credentials. The plan: first I'll confirm that Teams capture works with your service account and that the Zendesk search returns the right tickets on a few test cases. Then I'll add the matching rules and the internal note, and only after that the escalation and exception handling, proving each phase before moving on. At the end you receive the source code and short handover notes on how to run and change it. Which channels do your customers use to chase today: group chats, channel replies, or 1:1 chats? Sarel
₹20,889 INR in 14 days
0.0
0.0

Start with the Graph change notification subscription on the group chat, then test tickets, before anything touches live ones. Everything downstream hangs on getting the PNR and TKTN out cleanly. M1: Teams capture, PNR/TKTN/subject parsing, Search API match, proven on test tickets. 14850 INR. M2: Internal note, chaser counter, tags for the Customer Chasers view. 15000 INR. M3: Exception ticket when no confident match exists, retries so nothing is lost. 15150 INR. The 45000 is an indicator to get me talking, and it covers M1 plus a first slice of the rest. The full job gets priced once I see how messy the real chaser messages are and how many matching edge cases there are. It holds if your Zendesk admin creates the custom fields, tags, views and OAuth credentials, the tenant admin grants Graph consent for the service account, chasers sit in group chats that account already belongs to (no channels, shared channels or 1:1), and v1 is rule-based with the alert and exception SLA triggers left in Zendesk. If any of that differs, I re-quote before starting. Do the PNR and TKTN always sit in the message text, or sometimes in attachments? Should two tickets sharing a PNR count as no confident match? Are chasers ever thread replies? Roughly how many chats are being watched?
₹45,000 INR in 3 days
1.4
1.4

Hi Edwin, your brief is unusually clear and the architecture is right (automation updates the ticket, native Zendesk triggers handle routing, no webhooks back into the same ticket). I'd build it as a small, reliable Node service. How I'd build it: 1. Capture: Microsoft Graph change notifications on the service account's group chats via the dedicated integration identity, with subscription renewal and a catch up poll so no message is missed. 2. Filtering: only customer messages count as chasers; agents, bots and system messages are ignored. 3. Extraction and matching: PNR and ticket number patterns first, subject keywords as fallback, then Zendesk search. Ambiguous or multiple matches are not guessed: they go to a small "needs review" log. 4. Update: set Teams Chaser, increment Teams Chaser Count, stamp Last Teams Chaser, and add an internal note quoting the chase with a link to the Teams message. Duplicate suppression uses the Last Teams Chaser window you define, and every update is idempotent. 5. Zendesk side: I'll set up the custom fields, the trigger and the Customer Chasers view exactly as in your brief. 6. Ops: structured logs, retries with backoff for Graph and Zendesk rate limits, alerting on failures, a short runbook, deployed on Azure Functions or a small container. Timeline: working end to end on a test chat in 5 days, production ready in 7. I'm building my Freelancer profile (my first two projects here both got 5 stars), so I'm pricing this below my usual rate in exchange for an honest review. Roughly how many customer group chats does the service account sit in, and is there a Microsoft 365 admin who can grant app consent?
₹15,000 INR in 7 days
0.0
0.0

Hello! Your chat chasers updating the right Zendesk ticket, ready 6 days after we get access. You pay us nothing until you've seen it working. Here is what you get: • Day 2 after access: a chaser's PNR is found and an internal note lands on the ticket • Chaser count, your match rules and the escalation tiers for your Zendesk views • Unmatched chasers become exception tickets, with the 2-3 minute search retry • Full source code plus a setup guide for your Zendesk admin Good to know: reading customer chats needs your Microsoft admin's consent. 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. Bonus: a one-page runbook for the person who owns the Unmatched view each shift. Our own demo: an order sync between two systems that survives duplicates and outages. Price: ₹12,500, 45% off our regular ₹24,900, our introductory price. Do your customers chase only in group chats, or in channels and 1:1 chats too? P.S. Oldrich, the owner, directs the work and stands behind every result. We work with the help of modern technologies, including AI, which keeps us fast and precise.
₹12,500 INR in 6 days
0.0
0.0

Hi Edwin, Aleks from UZYTAK. I'd build it exactly on your architecture: 1. Capture: Microsoft Graph change notifications on the service account's group chats (with renewal), OAuth on a dedicated integration identity. 2. Extract PNR / ticket no. / subject (regex + fuzzy subject fallback). 3. Match via Zendesk Search API with a clear Teams Match Status (matched / multiple / not found). 4. Update via Zendesk API only: Teams Chaser, Count +1, Last Teams Chaser, internal note with chat link; duplicate suppression, idempotent per message ID. 5. Native triggers + Customer Chasers view do routing/priority, no webhooks back into the same ticket. 6. n8n or a small Python/Azure Function, with logs, retries and a short runbook. UZYTAK is a registered EU company (Poland), new on Freelancer, so we do top quality at your budget: reputation and reviews matter to us. Revisions until you accept, 6 months free bug fixes, payment only after acceptance. Usually 3-4 working days after access to a test tenant and Zendesk sandbox. Question: n8n, Power Automate or code - which do you prefer? Aleks, UZYTAK
₹25,000 INR in 8 days
0.0
0.0

Your Teams chaser to Zendesk flow, where a customer chase is matched by PNR or ticket number and the right ticket rises in a Customer Chasers view, is a tidy integration that I can build cleanly. I would capture Teams group chat messages through Microsoft Graph change notifications on a dedicated service account, extract the PNR or ticket number with a small parser, search Zendesk through its API, and update the custom fields and tags additively so existing tags stay untouched. Unmatched messages would get the unmatched tag for manual review, with duplicate suppression using the Last Teams Chaser time, and Zendesk triggers would handle priority and routing afterwards as you described. I would run it in Node with OAuth credentials on an integration identity, plus logging and retries. I bring 9 years of full-stack work with React, Node, Python, Flutter and AI/ML, plus B2B and e-commerce systems. Two questions: do you prefer a hosted automation tool or a small custom service on your own cloud, and do your PNR formats follow one fixed pattern? Happy to go through details with you here on Freelancer.
₹18,000 INR in 14 days
0.0
0.0

Hi, I will build Phase 1 of your Teams-to-Zendesk chaser automation as you have laid it out: capture, PNR extraction, Zendesk search, internal note. Phase 1: capture each new customer message from the service account's Teams chats (Microsoft Graph chat notifications), clean the HTML to plain text, extract the 6-character PNR after "PNR:" and the full TKTN string, search Zendesk by PNR (Search API, one retry after 2-3 minutes for index lag), and on a match add a private internal note ("public": false) in your example format. I also create the Zendesk fields (Teams Chaser, Count, Last Chaser, Match Status) and the teams_chaser tag, added without overwriting existing tags. OAuth runs on the dedicated integration identity, and everything is proven on test tickets before live ones. We have done similar integrations for existing clients, but they are under confidentiality agreements, so I cannot share them; I can walk you through the architecture. INR 12,500 for Phase 1, 4 days once the service account and Zendesk admin access are ready. Phases 2 and 3 (matching rules, views, escalation, unmatched workflow) are quoted after Phase 1 is proven. Can your Microsoft 365 admin grant tenant consent for Graph chat access, or should I use Power Automate? Aakaash
₹12,500 INR in 4 days
0.0
0.0

Gurgaon, India
Member since Jan 24, 2019
₹12500-37500 INR
₹600-1500 INR
₹12500-37500 INR
min $50 CAD / hour
$15-25 USD / hour
$100-1500 USD
$250-750 USD
₹12500-37500 INR
€30-250 EUR
$30-250 USD
$15-25 CAD / hour
₹1500-12500 INR
$30-250 USD
₹12500-37500 INR
₹12500-37500 INR
₹1500-12500 INR
$30-250 USD
₹1500-12500 INR
min $100000 USD
₹250000-500000 INR
$250-750 USD