Adding Dependencies on Story for Effective Management

Although provided format is familiar with all of us when I talk about writing user stories, sometime you might see that you get lot many queries from team when it comes to dependencies with third party system.  So to avoid such incident, can we add one more segment on story level , which specifically talks about it ? like dependencies with system, Point of contact and Expected ETA to resolve it

Example : 

Story Description

1. As auser type>, I want to function> so that benefit> 
2. As a role>, I can feature> so that reason>

 Acceptance Criteria

1. Scenario 1: Title
   Given [context]
   And [some more context]…
   When [event]
   Then [outcome]
   And [another outcome]…

1. Scenario 1: Title
   Given [context]
   And [some more context]…
   When [event]
   Then [outcome]
   And [another outcome]…

Dependencies with

• System 1: for Expectation> POC to Resolve Name, e-mail Id and Contact no.> ETA in Days>
• System 2: for Expectation> POC to Resolve Name, e-mail Id and Contact no.> ETA in Days>

Hope this will help you to reduce dependencies, and get effective transaction of stories.